GHSA-wcr3-9x4c-f5gj
GHSA-wcr3-9x4c-f5gj is a security vulnerability in github.com/blnkfinance/blnk. O3 Security confirms whether GHSA-wcr3-9x4c-f5gj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Blnk has an API key authorization bypass in owner and scope enforcement
Real-World Exposure
github.com/blnkfinance/blnkReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Blnk API key endpoints had an authorization issue that allowed non-master API keys to perform key-management actions outside their intended authorization boundary.
In affected versions, API key operations trusted caller-controlled request values for owner and scope decisions. As a result, a non-master API key could potentially manage keys for another owner by supplying a different owner value, or create a more privileged API key by requesting broader scopes than it already had.
This has been fixed by deriving the effective owner from the authenticated API key and enforcing scope coverage checks when creating new keys.
Details
The API key authorization flow previously trusted request data supplied by the caller when deciding which owner a key-management operation applied to and which scopes could be granted.
This meant a non-master API key could potentially:
- create API keys for another owner
- list API keys belonging to another owner
- revoke API keys belonging to another owner
- create a new API key with broader scopes than the caller’s own scopes
The patched version changes this behavior for non-master API keys:
- the effective owner is derived from the authenticated API key
- caller-supplied owner values are no longer trusted for authorization decisions
- cross-owner key operations are rejected with
403 Forbidden - requested scopes must be covered by the caller’s existing scopes
- master-key behavior is unchanged
Impact
A non-master API key with access to API key management endpoints could potentially perform unauthorized key-management operations across owners or escalate its permissions by creating a new API key with broader scopes.
Deployments using API keys for programmatic key creation, listing, or revocation should upgrade.
Affected versions
Versions up to and including v0.14.2 are affected.
Patched versions
This issue is fixed in v0.14.3.
Users should upgrade to v0.14.3 or later.
Workarounds
If developers cannot upgrade their applications immediately, restrict access to API key management endpoints to trusted master keys only.
Where possible, disable or block non-master API key access to key creation, listing, and revocation endpoints until the patched version is deployed.
Credits
Blank thanks @Shivam8584 for identifying and fixing this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/blnkfinance/blnk | all versions | 0.14.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/blnkfinance/blnk. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/blnkfinance/blnk to 0.14.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wcr3-9x4c-f5gj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-wcr3-9x4c-f5gj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-wcr3-9x4c-f5gj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-wcr3-9x4c-f5gj in your dependencies?
O3 detects GHSA-wcr3-9x4c-f5gj across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.