{"answers":{"affected":"3 open source packages ship an affected version, including onefuzz. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-37705 in the wild and no public exploit code.","fix":"Upgrade onefuzz to 2.31.0 or later.","what":"CVE-2021-37705 is a critical missing authorization vulnerability in microsoft onefuzz, published on 13 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-37705 and fix it if it is affected.\n\nWhat it is: CVE-2021-37705 is a critical missing authorization vulnerability in microsoft onefuzz, published on 13 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-37705 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- onefuzz (PyPI): affected from 2.12.0; fixed in 2.31.0\n- onefuzz (PyPI): affected from 2.12.0; fixed in 2.31.0\n- onefuzz (PyPI): affected from 2.12.0; fixed in 2.31.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-37705/ (Markdown: https://insights.sbomify.com/CVE-2021-37705/index.md)","id":"CVE-2021-37705","markdown":"https://insights.sbomify.com/CVE-2021-37705/index.md","name":"CVE-2021-37705","record":{"aliases":["GHSA-q5vh-6whw-x745","PYSEC-2021-344"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","data_modify","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"OneFuzz fuzzing platform","requires_auth":"none","summary":"Authenticated users from any Azure AD tenant can access private data and execute code on Azure resources if OneFuzz is deployed with multi-tenant support enabled.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"onefuzz","vendor":"microsoft"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"},{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"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 \u003c 2.31.0 by redeploying in the default configuration, which omits the `--multi_tenant_domain` option.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Authorization and Origin Validation Error in OneFuzz","id":"CVE-2021-37705","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":3,"n_references":5,"next":{"headline":"Potential integer underflow upon receiving STUN message in PJSIP","id":"CVE-2021-37706"},"packages":[{"ecosystem":"PyPI","fixed":["2.31.0"],"introduced":["2.12.0"],"last_affected":[],"package":"onefuzz","purl":null,"source":"GHSA-q5vh-6whw-x745"},{"ecosystem":"PyPI","fixed":["2.31.0"],"introduced":["2.12.0"],"last_affected":[],"package":"onefuzz","purl":"pkg:pypi/onefuzz","source":"GHSA-q5vh-6whw-x745"},{"ecosystem":"PyPI","fixed":["2.31.0"],"introduced":["2.12.0"],"last_affected":[],"package":"onefuzz","purl":"pkg:pypi/onefuzz","source":"PYSEC-2021-344"}],"prev":{"headline":"Exposed phpinfo() in PhpFastCache","id":"CVE-2021-37704"},"products":["onefuzz"],"published":"2021-08-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["microsoft"]},"summary":"Authenticated users from any Azure AD tenant can access private data and execute code on Azure resources if OneFuzz is deployed with multi-tenant support enabled.","url":"https://insights.sbomify.com/CVE-2021-37705/"}