Code execution via out-of-bounds UAS read
Published Mar 12, 2024 · Updated May 3, 2025
Out-of-bounds read in Windows UAS protocol handling allows physically proximate attackers to execute code through a malicious USB device. Microsoft maps the issue to an out-of-bounds read but does not disclose the driver routine, malformed UAS field, or failed bounds check. Exploitation requires physical access and a crafted UAS-capable USB device; the vendor assessment bounds the reported impact to confidentiality and integrity loss without service interruption.
Summary
What happened
Out-of-bounds read in Windows UAS protocol handling allows physically proximate attackers to execute code through a malicious USB device. Microsoft maps the issue to an out-of-bounds read but does not disclose the driver routine, malformed UAS field, or failed bounds check. Exploitation requires physical access and a crafted UAS-capable USB device; the vendor assessment bounds the reported impact to confidentiality and integrity loss without service interruption.
The record
- CVE
- CVE-2024-21430
- Published
- Mar 12, 2024
- Updated
- May 3, 2025
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-125, T1200
- Attack vector
- physical
- 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=10.0.10240.0 <10.0.10240.20526
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.
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