PYSEC-2021-344

See a problem?
Import Source
https://github.com/pypa/advisory-database/blob/main/vulns/onefuzz/PYSEC-2021-344.yaml
JSON Data
https://api.test.osv.dev/v1/vulns/PYSEC-2021-344
Aliases
Published
2021-08-13T21:15:00Z
Modified
2023-11-01T04:55:55.163875Z
Summary
[none]
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 --multitenantdomain 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

Affected packages

PyPI / onefuzz

Package

Affected ranges

Type
GIT
Repo
https://github.com/microsoft/onefuzz
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed
Type
ECOSYSTEM
Events
Introduced
2.12.0
Fixed
2.31.0

Affected versions

2.*

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