Cross-tenant code execution via unchecked token issuer
Published Aug 13, 2021 · Updated Aug 4, 2024
Improper authorization in Microsoft OneFuzz 2.12.0 through 2.30.0 allows remote authenticated users to execute code via API calls. The API authentication path accepts Azure Active Directory bearer tokens without comparing the issuer claim to an administrator-configured tenant allowlist. Exposure requires the non-default multi-tenant deployment option; any Azure Active Directory tenant account can read or alter private fuzzing data and run code on Azure compute resources.
Summary
What happened
Improper authorization in Microsoft OneFuzz 2.12.0 through 2.30.0 allows remote authenticated users to execute code via API calls. The API authentication path accepts Azure Active Directory bearer tokens without comparing the issuer claim to an administrator-configured tenant allowlist. Exposure requires the non-default multi-tenant deployment option; any Azure Active Directory tenant account can read or alter private fuzzing data and run code on Azure compute resources.
The record
- CVE
- CVE-2021-37705
- Published
- Aug 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- OneFuzz
- Classifications
- CWE-346, CWE-285, CWE-863, T1078.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.12.0, < 2.31.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo