Windows Routing and Remote Access Service (RRAS) Remote Code Execution Vulnerability
Released: Oct 8, 2024
- Assigning CNA
- Microsoft
- CVE.org link
- CVE-2024-38265
- Impact
- Remote Code Execution
- Max Severity
- Important
- Weakness
- CVSS Source
- Microsoft
- Vector String
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
- Metrics
- CVSS:3.1 8.8 / 7.7Base score metrics: 8.8 / Temporal score metrics: 7.7
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Exploit Code Maturity
Unproven
Remediation Level
Official Fix
Report Confidence
Confirmed
Please see Common Vulnerability Scoring System for more information on the definition of these metrics.
Exploitability
The following table provides an exploitability assessment for this vulnerability at the time of original publication.
- Publicly disclosed
- No
- Exploited
- No
- Exploitability assessment
- Exploitation Less Likely
FAQ
According to the CVSS metric, the attack vector is network (AV:N) and the user interaction is required (UI:R). What is the target context of the remote code execution?
This attack requires an admin user on the client to connect to a malicious server, and that could allow the attacker to gain code execution on the client.
How could an attacker exploit this vulnerability?
An unauthenticated attacker could send a specially crafted protocol message to a Routing and Remote Access Service (RRAS) server, which could lead to remote code execution (RCE) on the RAS server machine.
According to the CVSS metric, user interaction is required (UI:R). What interaction would the user have to do?
Exploitation of this vulnerability requires a user to remote into a server that is controlled by an attacker, which could then allow the server to execute a command on the user's machine without their consent. This scenario assumes that the user has the ability to remote into the server and that the server has been compromised to execute such commands upon connection.
Acknowledgements
- Anonymous
- Dan Reynolds with MSRC Vulnerabilities & Mitigations
Security Updates
To determine the support lifecycle for your software, see the Microsoft Support Lifecycle.
- 6.3.9600.22221
- 6.3.9600.22221
- 6.2.9200.25118
- 6.2.9200.25118
- 6.1.7601.27366
- 6.1.7601.27366
- 6.1.7601.27366
- 6.1.7601.27366
- 6.0.6003.22918
- 6.0.6003.22918
- 6.0.6003.22918
- 6.0.6003.22918
- 6.0.6003.22918
- 6.0.6003.22918
- 6.0.6003.22918
- 6.0.6003.22918
- 10.0.14393.7428
- 10.0.14393.7428
- 10.0.25398.1189
- 10.0.20348.2762
- 10.0.20348.2762
- 10.0.17763.6414
- 10.0.17763.6414
Disclaimer
Revisions
Information published.