CVE-2017-7269
KEVMicrosoft Windows Server Buffer Overflow Vulnerability
Description
Microsoft Windows Server 2003 R2 contains a buffer overflow vulnerability in Internet Information Services (IIS) 6.0 which allows remote attackers to execute code via a long header beginning with "If: <http://" in a PROPFIND request.
Buffer overflow in the ScStoragePathFromUrl function in the WebDAV service in Internet Information Services (IIS) 6.0 in Microsoft Windows Server 2003 R2 allows remote attackers to execute arbitrary code via a long header beginning with "If: <http://" in a PROPFIND request, as exploited in the wild in July or August 2016.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HPublishedMar 27, 2017
Last modifiedJun 17, 2026
Added to KEVNov 3, 2021
Remediation dueMay 3, 2022
References
- securityfocus.com/bid/97127Broken LinkThird Party Advisory
- securitytracker.com/id/1038168Broken LinkThird Party Advisory
- 0patch.blogspot.com/2017/03/0patching-immortal-cve-2017-7269.htmlExploitThird Party Advisory
- github.com/danigargu/explodingcanExploit
- github.com/edwardz246003/IIS_exploitBroken LinkThird Party Advisory
- github.com/rapid7/metasploit-framework/pull/8162Issue TrackingPatch
- medium.com/%40iraklis/number-of-internet-facing-vulnerable-iis-6-0-to-cve-2017-7269-8bd153ef5812Exploit
- support.microsoft.com/en-us/help/3197835/description-of-the-security-update-for-windows-xp-and-windows-serverBroken LinkPatch
- exploit-db.com/exploits/41738/ExploitThird Party Advisory
- exploit-db.com/exploits/41992/ExploitThird Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2017-7269US Government Resource
0 recent articles mention this CVE
89
Risk assessment · Critical
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1637 days
- CVSS
- 9.8 CRITICAL
- EPSS (30-day exploit probability)
- 99.8% · top 1% of all CVEs
- Weakness
- CWE-120
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
Recommended actions
- 1.Apply updates per vendor instructions.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.