PYSEC-2021-344

Vulnerability from pysec - Published: 2021-08-13 21:15 - Updated: 2021-09-26 23:32
VLAI?
Details

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.

Impacted products
Name purl
onefuzz pkg:pypi/onefuzz
Aliases
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "onefuzz",
        "purl": "pkg:pypi/onefuzz"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2fcb4998887959b4fa11894a068d689189742cb1"
            }
          ],
          "repo": "https://github.com/microsoft/onefuzz",
          "type": "GIT"
        },
        {
          "events": [
            {
              "introduced": "2.12.0"
            },
            {
              "fixed": "2.31.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "2.12.0",
        "2.13.0",
        "2.14.0",
        "2.15.0",
        "2.16.0",
        "2.17.0",
        "2.18.0",
        "2.19.0",
        "2.20.0",
        "2.21.0",
        "2.22.0",
        "2.23.0",
        "2.23.1",
        "2.24.0",
        "2.25.0",
        "2.25.1",
        "2.26.0",
        "2.26.1",
        "2.27.0",
        "2.28.0",
        "2.29.0",
        "2.29.1",
        "2.30.0"
      ]
    }
  ],
  "aliases": [
    "CVE-2021-37705",
    "GHSA-q5vh-6whw-x745"
  ],
  "details": "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\u0027s `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.",
  "id": "PYSEC-2021-344",
  "modified": "2021-09-26T23:32:40.198740Z",
  "published": "2021-08-13T21:15:00Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/microsoft/onefuzz/releases/tag/2.31.0"
    },
    {
      "type": "WEB",
      "url": "https://github.com/microsoft/onefuzz/pull/1153"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/onefuzz/"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/microsoft/onefuzz/security/advisories/GHSA-q5vh-6whw-x745"
    },
    {
      "type": "FIX",
      "url": "https://github.com/microsoft/onefuzz/commit/2fcb4998887959b4fa11894a068d689189742cb1"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.