Code execution by physically proximate attackers
Published Oct 8, 2024 · Updated Aug 19, 2026
Heap-based buffer overflow in the Windows Mobile Broadband Driver allows physically proximate attackers to execute code on affected systems. Microsoft identifies improper input validation but has not published the specific driver routine, input field, or incorrect operation that corrupts heap memory. Exploitation requires physical access to the system and can compromise code execution, data, and service availability.
Summary
What happened
Heap-based buffer overflow in the Windows Mobile Broadband Driver allows physically proximate attackers to execute code on affected systems. Microsoft identifies improper input validation but has not published the specific driver routine, input field, or incorrect operation that corrupts heap memory. Exploitation requires physical access to the system and can compromise code execution, data, and service availability.
The record
- CVE
- CVE-2024-43526
- Published
- Oct 8, 2024
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-20, CWE-122, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 8, 2024CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record 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.6414
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