Unauthenticated confidential-data disclosure via undisclosed spoofing
Published Mar 12, 2024 · Updated May 3, 2025
Spoofing in Microsoft Azure SDK 1.0.0 through 1.29.4 allows remote attackers to disclose confidential data via network requests. Microsoft has not published the affected library or dependency, the faulty operation, or how untrusted network input is accepted as authentic. Exploitation requires a network-reachable application using an affected SDK release; no privileges or user interaction are required, and the reported consequence is confidentiality loss only.
Summary
What happened
Spoofing in Microsoft Azure SDK 1.0.0 through 1.29.4 allows remote attackers to disclose confidential data via network requests. Microsoft has not published the affected library or dependency, the faulty operation, or how untrusted network input is accepted as authentic. Exploitation requires a network-reachable application using an affected SDK release; no privileges or user interaction are required, and the reported consequence is confidentiality loss only.
The record
- CVE
- CVE-2024-21421
- Published
- Mar 12, 2024
- Updated
- May 3, 2025
- Vendor
- Microsoft
- Product
- Azure SDK
- Classifications
- CWE-1395
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2024CVE publishedPublication date reported by the CVE source.
- May 3, 2025Record 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=1.0.0 <1.29.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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