CVE-2024-38128: Windows Routing and Remote Access Service (RRAS) Remote Code Execution Vulnerability
Published Aug 13, 2024
·Updated
Windows Routing and Remote Access Service (RRAS) Remote Code Execution Vulnerability
Affected Software
25 affected componentsFixes available
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2022, 23H2 Edition
Microsoft Windows Server 2012
Microsoft Windows Server 2012
Microsoft Windows Server 2008
Microsoft Windows Server 2008
Microsoft Windows Server 2008
Microsoft Windows Server 2008
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=r2-sp1
Microsoft Windows Server 2012<6.2.9200.25031
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.7259
Microsoft Windows Server 2019<10.0.17763.6189
Microsoft Windows Server 2022<10.0.20348.2655
Microsoft Windows Server 2022 23h2<10.0.25398.1085
Microsoft Windows Server 2019
Microsoft Windows Server 2019
Microsoft Windows Server 2022
Microsoft Windows Server 2022
Microsoft Windows Server 2016
Microsoft Windows Server 2016
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2008 R2
Remediation
Event History
Aug 13, 2024
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
CVE Published
via MITRE·05:30 PM
Data Sourced
via MITRE·05:30 PM
DescriptionSeverity
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2024-38128?
CVE-2024-38128 is classified as a critical vulnerability due to its potential for remote code execution.
2
How do I fix CVE-2024-38128?
To address CVE-2024-38128, apply the latest security updates from Microsoft for affected products.
3
What products are affected by CVE-2024-38128?
CVE-2024-38128 affects various versions of Microsoft Windows Server including 2008, 2012, 2016, 2019, and 2022.
4
What is the impact of CVE-2024-38128 on my system?
Exploitation of CVE-2024-38128 could allow an attacker to execute arbitrary code on the affected system.
5
Is there a workaround for CVE-2024-38128?
Currently, the best mitigation for CVE-2024-38128 is to apply the security updates as there are no known effective workarounds.