GHSA-q5vh-6whw-x745 is a critical-severity (CVSS 10) CWE-285 vulnerability in onefuzz. O3 Security confirms whether GHSA-q5vh-6whw-x745 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Improper Authorization and Origin Validation Error in OneFuzz
Real-World Exposure
onefuzzReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Starting with OneFuzz 2.12.0 or greater, an incomplete authorization check allows an authenticated user from any Azure Active Directory tenant to make authorized API calls to a vulnerable OneFuzz instance.
To be vulnerable, a OneFuzz deployment must be:
- Version 2.12.0 or greater
- Deployed with the non-default
--multi_tenant_domainoption
This can result in read/write access to private data such as:
- Software vulnerability and crash information
- Security testing tools
- Proprietary code and symbols
Via authorized API calls, this also enables tampering with existing data and unauthorized code execution on Azure compute resources.
Patches
This issue is resolved starting in release 2.31.0, via the addition of application-level check of the bearer token's issuer against an administrator-configured allowlist.
Workarounds
Users can restrict access to the tenant of a deployed OneFuzz instance < 2.31.0 by redeploying in the default configuration, which omits the --multi_tenant_domain option.
References
You can find an overview of the Microsoft Identity Platform here. This vulnerability applies to the multi-tenant application pattern, as described here.
For more information
If you have any questions or comments about this advisory:
- Open an issue in OneFuzz
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | onefuzz | ≥ 2.12.0&&< 2.31.0 | 2.31.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for onefuzz. 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 onefuzz to 2.31.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q5vh-6whw-x745 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-q5vh-6whw-x745 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-q5vh-6whw-x745. 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-q5vh-6whw-x745 in your dependencies?
O3 detects GHSA-q5vh-6whw-x745 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.