CVE-2024-30012

Physical code execution via undisclosed integer overflow

Published May 14, 2024 · Updated May 3, 2025

Integer overflow in the Windows Mobile Broadband Driver allows physically proximate attackers to execute code through a malicious USB device. Microsoft identifies the weakness class but has not published the affected routine or the incorrect arithmetic operation on device input. Exploitation requires unauthenticated physical access to connect the device, after which code execution can compromise the Windows host.

CVSS severity6.8
Medium
EPSS probability0.87%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Integer overflow in the Windows Mobile Broadband Driver allows physically proximate attackers to execute code through a malicious USB device. Microsoft identifies the weakness class but has not published the affected routine or the incorrect arithmetic operation on device input. Exploitation requires unauthenticated physical access to connect the device, after which code execution can compromise the Windows host.

The record

CVE
CVE-2024-30012
Published
May 14, 2024
Updated
May 3, 2025
Vendor
Microsoft
Product
Windows Server 2019
Classifications
CWE-190, T1200
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 14, 2024CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=10.0.17763.0 <10.0.17763.5820

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

Microsoft · Windows Server 2019version=10.0.17763.0 <10.0.17763.5820
Microsoft · Windows 11 version 21H2version=10.0.0 <10.0.22000.2960
Microsoft · Windows 10 Version 21H2version=10.0.19043.0 <10.0.19044.4412
Microsoft · Windows Server 2022, 23H2 Edition (Server Core installation)version=10.0.25398.0 <10.0.25398.887
Microsoft · Windows 11 Version 22H3version=10.0.22631.0 <10.0.22631.3593
Microsoft · Windows 10 Version 22H2version=10.0.19045.0 <10.0.19045.4412
Microsoft · Windows Server 2019 (Server Core installation)version=10.0.17763.0 <10.0.17763.5820
Microsoft · Windows 11 Version 23H2version=10.0.22631.0 <10.0.22631.3593
Microsoft · Windows 11, version 22H2version=10.0.22621.0 <10.0.22621.3593
Microsoft · Windows Server 2022version=10.0.20348.0 <10.0.20348.2461
Microsoft · Windows 10 Version 1809version=10.0.0 <10.0.17763.5820; version=10.0.17763.0 <10.0.17763.5820

Published CVSS scores

6.8Microsoft CorporationCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-190Integer Overflow or Wraparound
T1200Hardware Additions

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