Django REST framework

Package Instance

Lookup for vulnerable packages by Package URL.

Purlpkg:pypi/onefuzz@2.16.0
Typepypi
Namespace
Nameonefuzz
Version2.16.0
Qualifiers
Subpath
Is_vulnerabletrue
Next_non_vulnerable_version2.31.0
Latest_non_vulnerable_version2.31.0
Affected_by_vulnerabilities
0
url VCID-du75-sysn-wkaa
vulnerability_id VCID-du75-sysn-wkaa
summary 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.
references
0
reference_url https://github.com/microsoft/onefuzz
reference_id
reference_type
scores
url https://github.com/microsoft/onefuzz
1
reference_url https://github.com/microsoft/onefuzz/commit/2fcb4998887959b4fa11894a068d689189742cb1
reference_id
reference_type
scores
url https://github.com/microsoft/onefuzz/commit/2fcb4998887959b4fa11894a068d689189742cb1
2
reference_url https://github.com/microsoft/onefuzz/pull/1153
reference_id
reference_type
scores
url https://github.com/microsoft/onefuzz/pull/1153
3
reference_url https://github.com/microsoft/onefuzz/releases/tag/2.31.0
reference_id
reference_type
scores
url https://github.com/microsoft/onefuzz/releases/tag/2.31.0
4
reference_url https://github.com/microsoft/onefuzz/security/advisories/GHSA-q5vh-6whw-x745
reference_id
reference_type
scores
url https://github.com/microsoft/onefuzz/security/advisories/GHSA-q5vh-6whw-x745
5
reference_url https://github.com/pypa/advisory-database/tree/main/vulns/onefuzz/PYSEC-2021-344.yaml
reference_id
reference_type
scores
url https://github.com/pypa/advisory-database/tree/main/vulns/onefuzz/PYSEC-2021-344.yaml
6
reference_url https://pypi.org/project/onefuzz
reference_id
reference_type
scores
url https://pypi.org/project/onefuzz
7
reference_url https://pypi.org/project/onefuzz/
reference_id
reference_type
scores
url https://pypi.org/project/onefuzz/
8
reference_url https://nvd.nist.gov/vuln/detail/CVE-2021-37705
reference_id CVE-2021-37705
reference_type
scores
url https://nvd.nist.gov/vuln/detail/CVE-2021-37705
9
reference_url https://github.com/advisories/GHSA-q5vh-6whw-x745
reference_id GHSA-q5vh-6whw-x745
reference_type
scores
url https://github.com/advisories/GHSA-q5vh-6whw-x745
fixed_packages
0
url pkg:pypi/onefuzz@2.31.0
purl pkg:pypi/onefuzz@2.31.0
is_vulnerable false
affected_by_vulnerabilities
resource_url http://public2.vulnerablecode.io/packages/pkg:pypi/onefuzz@2.31.0
aliases CVE-2021-37705, GHSA-q5vh-6whw-x745, PYSEC-2021-344
risk_score null
exploitability null
weighted_severity null
resource_url http://public2.vulnerablecode.io/vulnerabilities/VCID-du75-sysn-wkaa
Fixing_vulnerabilities
Risk_scorenull
Resource_urlhttp://public2.vulnerablecode.io/packages/pkg:pypi/onefuzz@2.16.0