Vulnerabilities in pkg:pypi/onefuzz

PACKAGE
Advisory Identifier: GHSA-q5vh-6whw-x745
Advisory Summary

CVE-2021-37705 is a CRITICAL (CVSS 10.0) improper authorization and origin validation vulnerability (CWE-285: Improper Authorization) affecting Onefuzz libraries in the PyPI ecosystem. The issue involves improper authorization and origin validation error in onefuzz. Remediation is available by upgrading affected packages to version 2.31.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:pypi/onefuzz

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:pypi/onefuzz. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-q5vh-6whw-x745 CVE-2021-37705 CRITICAL Improper Authorization and Origin Validation Error in OneFuzz

CVE-2021-37705 at a Glance

CVE Identifier CVE-2021-37705
GHSA Identifier GHSA-q5vh-6whw-x745
Severity CRITICAL
CVSS v3.1 Base Score 10.0
CWE Classification CWE-285: Improper Authorization
Affected Product Onefuzz
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 10.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability Low (A:L)

How to Fix CVE-2021-37705

To remediate this vulnerability, upgrade all affected Onefuzz dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

onefuzz fixed: 2.31.0
pip install onefuzz>=2.31.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show onefuzz

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2021-37705, inspect your installed packages using pip:

pip show onefuzz

Analyze the terminal output to locate any version of Onefuzz in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.31.0), your application is affected.

Note: The pip show onefuzz command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-285: Improper Authorization, where the product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. In Onefuzz, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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_domain`](https://github.com/microsoft/onefuzz/blob/2.30.0/src/deployment/deploy.py#L1021) option 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](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-overview). This vulnerability applies to the multi-tenant application pattern, as described [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant). ## For more information If you have any questions or comments about this advisory: * Open an issue in [OneFuzz](https://github.com/microsoft/onefuzz) * Email us at [fuzzing@microsoft.com](mailto:fuzzing@microsoft.com)

CVE-2021-37705 Affected Onefuzz Versions

1 component(s)
Fixed Versions:
2.31.0
Product / Package Ecosystem Affected Versions Fixed Version
onefuzz
PyPI
≥ 2.12.0
< 2.31.0
2.31.0

References

Frequently Asked Questions

What is CVE-2021-37705?
CVE-2021-37705 is a security vulnerability in Onefuzz involving Improper Authorization and Origin Validation Error in OneFuzz under CWE-285: Improper Authorization.
Which Onefuzz versions are affected?
Affected versions include releases prior to 2.31.0 across affected packages: onefuzz.
What version fixes CVE-2021-37705?
Upgrading to 2.31.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is onefuzz affected?
Yes, onefuzz is affected in releases prior to 2.31.0. Upgrade your dependency to 2.31.0 or later.
What is the CVSS score of CVE-2021-37705?
CVE-2021-37705 has a CVSS v3.1 base score of 10.0 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L.
What CWE is associated with CVE-2021-37705?
CVE-2021-37705 is classified under CWE-285: Improper Authorization (The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.).
How can I check PyPI dependencies for CVE-2021-37705?
Run the dependency tree command: 'pip show onefuzz'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q5vh-6whw-x745",
  "modified" : "2024-10-07T16:44:37Z",
  "published" : "2021-08-13T20:16:32Z",
  "aliases" : [ "CVE-2021-37705" ],
  "summary" : "Improper Authorization and Origin Validation Error in OneFuzz",
  "details" : "## Impact\n\nStarting 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.\n\nTo be vulnerable, a OneFuzz deployment must be:\n* Version 2.12.0 or greater\n* Deployed with the non-default [`--multi_tenant_domain`](https://github.com/microsoft/onefuzz/blob/2.30.0/src/deployment/deploy.py#L1021) option\n\nThis can result in read/write access to private data such as:\n* Software vulnerability and crash information\n* Security testing tools\n* Proprietary code and symbols\n\nVia authorized API calls, this also enables tampering with existing data and unauthorized code execution on Azure compute resources.\n\n## Patches\n\nThis 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.\n\n## Workarounds\n\nUsers 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.\n\n## References\n\nYou can find an overview of the Microsoft Identity Platform [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-overview).  This vulnerability applies to the multi-tenant application pattern, as described [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant).\n\n## For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [OneFuzz](https://github.com/microsoft/onefuzz)\n* Email us at [fuzzing@microsoft.com](mailto:fuzzing@microsoft.com)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "onefuzz"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.12.0"
      }, {
        "fixed" : "2.31.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/microsoft/onefuzz/security/advisories/GHSA-q5vh-6whw-x745"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2021-37705"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/microsoft/onefuzz/pull/1153"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/microsoft/onefuzz/commit/2fcb4998887959b4fa11894a068d689189742cb1"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/microsoft/onefuzz"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/microsoft/onefuzz/releases/tag/2.31.0"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/onefuzz/PYSEC-2021-344.yaml"
  }, {
    "type" : "WEB",
    "url" : "https://pypi.org/project/onefuzz"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-285", "CWE-346", "CWE-863" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-08-13T20:16:08Z",
    "nvd_published_at" : "2021-08-13T21:15:00Z"
  }
}