onefuzz
Affected
- introduced
2.12.0, fixed2.31.0(ecosystem)
Fixed versions
2.31.0
Fix
- Fixed version
2.31.0pip install --upgrade onefuzz==2.31.0
Advisory
Also known as: CVE-2021-37705, PYSEC-2021-344
Improper Authorization and Origin Validation Error in OneFuzz
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:
This can result in read/write access to private data such as:
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:
Critical Basis: The source's own band: CRITICAL
2.12.0, fixed 2.31.0 (ecosystem)2.31.0
2.31.0pip install --upgrade onefuzz==2.31.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0