Code execution via mobile broadband integer overflow
Published May 14, 2024 · Updated May 3, 2025
Integer overflow in Microsoft's Windows Mobile Broadband Driver allows physically proximate attackers to execute code on affected Windows builds. Microsoft identifies integer overflow or wraparound but has not published the driver routine, input field, or arithmetic operation involved. Physical proximity to the target is required; successful exploitation executes attacker-controlled code with confidentiality, integrity, and availability impact.
Summary
What happened
Integer overflow in Microsoft's Windows Mobile Broadband Driver allows physically proximate attackers to execute code on affected Windows builds. Microsoft identifies integer overflow or wraparound but has not published the driver routine, input field, or arithmetic operation involved. Physical proximity to the target is required; successful exploitation executes attacker-controlled code with confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2024-30000
- Published
- May 14, 2024
- Updated
- May 3, 2025
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-190, T1203
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 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.17763.0 <10.0.17763.5820
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