Skip to content
Fencer Vulns
medium 6.8

CVE-2024-29998 json

Windows Mobile Broadband Driver Remote Code Execution Vulnerability

published 2024-05-14 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-26969

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits
0
none known

Summary

Windows Mobile Broadband Driver Remote Code Execution Vulnerability

Patch / fix

  • Microsoft Windows 10 Version 1809 10.0.17763.5820
  • Microsoft Windows Server 2019 10.0.17763.5820
  • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.5820
  • Microsoft Windows Server 2022 10.0.20348.2461
  • Microsoft Windows 11 version 21H2 10.0.22000.2960
  • Microsoft Windows 10 Version 21H2 10.0.19044.4412
  • Microsoft Windows 11 version 22H2 10.0.22621.3593
  • Microsoft Windows 10 Version 22H2 10.0.19045.4412
  • Microsoft Windows 11 version 22H3 10.0.22631.3593
  • Microsoft Windows 11 Version 23H2 10.0.22631.3593
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.887

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.93% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA 3.1 6.8 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Windows 10 Version 1809
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2019 (Server Core installation)
  • Microsoft Windows Server 2022
  • Microsoft Windows 11 version 21H2
  • Microsoft Windows 10 Version 21H2
  • Microsoft Windows 11 version 22H2
  • Microsoft Windows 10 Version 22H2
  • Microsoft Windows 11 version 22H3
  • Microsoft Windows 11 Version 23H2
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.