CVE-2017-8461 in the critical feed json
Windows RPC with Routing and Remote Access enabled in Windows XP and Windows Server 2003 allows an attacker to execute code on a targeted R…
published 2017-06-15 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17411
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 20.4%
- EPSS 20.4% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Metasploit
Summary
Windows RPC with Routing and Remote Access enabled in Windows XP and Windows Server 2003 allows an attacker to execute code on a targeted RPC server which has Routing and Remote Access enabled via a specially crafted application, aka "Windows RPC Remote Code Execution Vulnerability."
Patch / fix
Timeline
- First public exploit (Metasploit exploit/windows/smb/smb_rras_erraticgopher)
- Published
Exploit prediction
20.41% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/smb/smb_rras_erraticgopher Microsoft Windows RRAS Service MIBEntryGet Overflow metasploit exploit, average rank, 2017-06-13
- packetstormsecurity.com http://packetstormsecurity.com/files/161672/Microsoft-Windows-RRAS-Service-MIBEntryGet-Overflow.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.9 | AV:L/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- Microsoft Corporation Microsoft Windows
References
-
support.microsoft.com
/en-us/help/4024323/security-update-of-windows-xp-and-windows-server-2003
patch, vendor-advisory
-
packetstormsecurity.com
/files/161672/Microsoft-Windows-RRAS-Service-MIBEntryGet-Overflow.html
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/99012
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1038701
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-8461
- NVD CVE-2017-8461
Fencer Intel 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.