CVE-2024-43549 Overview
CVE-2024-43549 is a remote code execution vulnerability in the Windows Routing and Remote Access Service (RRAS). The flaw affects supported Windows Server releases from Windows Server 2008 through Windows Server 2022 23H2. An unauthenticated attacker can target a vulnerable server over the network, but exploitation requires user interaction. Successful exploitation results in arbitrary code execution in the context of the RRAS service, with high impact to confidentiality, integrity, and availability. The underlying weakness is tracked as a stack-based buffer overflow [CWE-121]. Microsoft addressed the issue in the October 2024 Patch Tuesday cycle.
Critical Impact
A network-adjacent attacker can achieve arbitrary code execution on Windows Server systems running RRAS, leading to full compromise of confidentiality, integrity, and availability.
Affected Products
- Microsoft Windows Server 2008 SP2 (x86, x64) and Windows Server 2008 R2 SP1
- Microsoft Windows Server 2012 and Windows Server 2012 R2
- Microsoft Windows Server 2016, Windows Server 2019, Windows Server 2022, and Windows Server 2022 23H2
Discovery Timeline
- 2024-10-08 - CVE-2024-43549 published to NVD and addressed in Microsoft's October 2024 security update
- 2024-10-17 - Last updated in NVD database
Technical Details for CVE-2024-43549
Vulnerability Analysis
The vulnerability resides in the Windows Routing and Remote Access Service, a Windows Server role that provides routing, VPN, and dial-up remote access capabilities. RRAS parses a wide range of network protocol structures, and the affected code path mishandles attacker-controlled input on the stack. The result is a stack-based buffer overflow [CWE-121] that allows an attacker to corrupt return addresses or adjacent stack data and redirect execution.
Exploitation does not require prior authentication, but it does require a user on the target environment to interact with attacker-supplied content or initiate a connection that triggers the vulnerable code. Once exploited, the attacker runs code in the context of the RRAS service, which typically operates with elevated privileges on the host.
Root Cause
The root cause is improper validation of the size or structure of network input before it is copied into a fixed-size stack buffer inside RRAS. When the supplied data exceeds the buffer's bounds, adjacent stack memory is overwritten. Microsoft has not published implementation-level details, but the CWE-121 classification confirms a classic stack buffer overflow pattern.
Attack Vector
The attack vector is the network. An attacker delivers a malformed request to a Windows Server running RRAS, or convinces a user to connect to an attacker-controlled endpoint that sends the malicious payload. Because RRAS is exposed when the Remote Access role is enabled, servers acting as VPN gateways or routers are the primary targets. Servers without the RRAS role enabled are not exposed to this vulnerability.
No public proof-of-concept code is available, and the issue is not listed in the CISA Known Exploited Vulnerabilities catalog. See the Microsoft CVE-2024-43549 Advisory for vendor guidance.
Detection Methods for CVE-2024-43549
Indicators of Compromise
- Unexpected crashes or restarts of the RemoteAccess service or svchost.exe instances hosting RRAS
- New or unusual child processes spawned by the RRAS service host
- Outbound connections from RRAS service processes to unexpected destinations
- Anomalous inbound traffic on RRAS-related ports such as PPTP (1723/TCP) and L2TP/IPsec (1701/UDP, 500/UDP, 4500/UDP)
Detection Strategies
- Monitor Windows Event Logs for RemoteAccess and RasMan service faults, including Application Error events (Event ID 1000) referencing RRAS binaries
- Alert on process creation events where svchost.exe hosting RRAS spawns shells (cmd.exe, powershell.exe) or LOLBins
- Inspect network flows for malformed or oversized RRAS protocol traffic targeting affected servers
Monitoring Recommendations
- Inventory all Windows Servers with the Remote Access role installed and confirm patch status against the October 2024 Microsoft updates
- Correlate RRAS service crashes with subsequent authentication, lateral movement, or persistence activity on the same host
- Track outbound connectivity initiated by RRAS service processes and treat deviations from baseline as high-priority alerts
How to Mitigate CVE-2024-43549
Immediate Actions Required
- Apply the October 2024 Microsoft security update for every affected Windows Server version listed in the Microsoft CVE-2024-43549 Advisory
- Identify hosts with the Remote Access role enabled and prioritize them for patching
- Restrict inbound access to RRAS-related ports to known VPN clients and management networks only
Patch Information
Microsoft released fixes for CVE-2024-43549 as part of the October 8, 2024 security update cycle, covering Windows Server 2008 SP2, 2008 R2 SP1, 2012, 2012 R2, 2016, 2019, 2022, and 2022 23H2. Refer to the Microsoft Security Response Center advisory for the specific KB articles applicable to each Windows Server release.
Workarounds
- Disable the Routing and Remote Access service on servers that do not require VPN or routing functionality
- Use host-based firewall rules to block external access to RRAS protocols (PPTP, L2TP, SSTP, IKEv2) on systems pending patch deployment
- Place RRAS endpoints behind a network gateway that performs protocol validation and rate limiting
# Configuration example: disable RRAS on hosts where it is not required
# Run from an elevated PowerShell prompt
Get-Service -Name RemoteAccess
Stop-Service -Name RemoteAccess -Force
Set-Service -Name RemoteAccess -StartupType Disabled
# Optionally remove the Remote Access role
Uninstall-WindowsFeature -Name RemoteAccess -IncludeManagementTools
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

