CVE-2024-30004: Windows Mobile Broadband Driver Remote Code Execution Vulnerability
Published May 14, 2024
·Updated
Windows Mobile Broadband Driver Remote Code Execution Vulnerability
Affected Software
29 affected componentsFixes available
Microsoft Windows Server 2022, 23H2 Edition
Microsoft Windows Server 2019
Microsoft Windows Server 2019
Microsoft Windows 11=23H2
Microsoft Windows 11=23H2
Microsoft Windows 11=22H2
Microsoft Windows 11=22H2
Microsoft Windows 11=21H2
Microsoft Windows 11=21H2
Microsoft Windows Server 2022
Microsoft Windows Server 2022
Microsoft Windows 10 1809<10.0.17763.5820
Microsoft Windows 10 21h2<10.0.19044.4412
Microsoft Windows 10 22h2<10.0.19045.4412
Microsoft Windows 11 21h2<10.0.22000.2960
Microsoft Windows 11 22h2<10.0.22621.3593
Microsoft Windows 11 23h2<10.0.22631.3593
Microsoft Windows Server 2019<10.0.17763.5820
Microsoft Windows Server 2022<10.0.20348.2458
Microsoft Windows Server 2022 23h2<10.0.25398.887
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows 10=22H2
Microsoft Windows 10=22H2
Microsoft Windows 10=22H2
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Remediation
Event History
May 14, 2024
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
CVE Published
via MITRE·04:57 PM
Data Sourced
via MITRE·04:57 PM
DescriptionSeverity
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2024-30004?
CVE-2024-30004 is rated as a critical vulnerability due to its potential for remote code execution.
2
How do I fix CVE-2024-30004?
To mitigate CVE-2024-30004, apply the security patches provided by Microsoft for affected Windows versions.
3
Which Windows versions are affected by CVE-2024-30004?
CVE-2024-30004 affects various versions of Windows 10 and Windows 11, including specific builds of Windows Server.
4
What are the potential impacts of CVE-2024-30004?
If exploited, CVE-2024-30004 could allow an attacker to execute arbitrary code on the affected system.
5
Is there a workaround for CVE-2024-30004?
Currently, there are no known workarounds for CVE-2024-30004, so patching is the recommended solution.