cve.bz

CVE-2021-37705 microsoft onefuzz: Incorrect Authorization

10.0 criticalEPSS 2.4%Fix available

Critical (10.0) in microsoft onefuzz. EPSS 2.4% estimated probability of exploitation activity in the next 30 days. Fixed in onefuzz 2.31.0.

On this page
OneFuzz is an open source self-hosted Fuzzing-As-A-Service platform. 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 both version 2.12.0 or greater and deployed with the non-default --multi_tenant_domain option. This can result in read/write access to private data such as software vulnerability and crash information, security testing tools and proprietary code and symbols. Via authorized API calls, this also enables tampering with existing data and unauthorized code execution on Azure compute resources. 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. As a workaround 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.

Severity

CVSS 3.1

10.0 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
2.4% (unchanged from 2.4% a week ago; 2.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 85th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-863 Incorrect Authorization
CWE-285 Improper Authorization
CWE-346 Origin Validation Error
OWASP Top 10
A01:2025 Broken Access Control, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2021-37705 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-37705?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-37705?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-37705 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
microsoft:onefuzzfrom 2.12.0 before 2.31.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-q5vh-6whw-x745PyPIonefuzz>=2.12.0 <2.31.02.31.0
PYSEC-2021-344PyPIonefuzz>=2.12.0 <2.31.02.31.0

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-285 (16), CWE-346 (16).

References

Check your stackJSON