CriticalCVE-2017-7269

    Microsoft Windows Server Buffer Overflow Vulnerability (CVE-2017-7269)

    Published In CISA KEV since Sources: CVE.org

    What is affected, what to do

    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.

    The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Microsoft Internet Information Services (IIS) eq 6.0..6.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org

    99.82 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.96

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    228.94 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    99.82 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.96
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 4 February 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-120

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw is network-reachable without authentication or user interaction and yields full host compromise. A public exploit and a Metasploit module have circulated since 2017, and automated mass scanners, cryptomining and botnet operators keep hitting it. It sits among the CVEs most likely to be exploited, even though CISA lists no known ransomware use. Typical victims are forgotten legacy web servers, line-of-business apps in industrial and public-sector estates, and appliances built on Server 2003. Any exposed IIS 6.0 host with WebDAV enabled is a drop-everything critical. If you have no IIS 6.0 in the estate, the work reduces to a one-off inventory confirmation.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Find every instance: Identify all Windows Server 2003 / 2003 R2 hosts running IIS 6.0, using the CMDB, Nmap (http-webdav-scan, http-server-header matching Microsoft-IIS/6.0) or your external attack-surface scanner. Treat any internet-facing hit as compromised until proven otherwise.
      • Kill WebDAV now: In IIS Manager, open "Web Service Extensions", set "WebDAV" to "Prohibited" and run iisreset. This removes the vulnerable ScStoragePathFromUrl code path from reach.
      • Check for the vendor fix: Microsoft released an out-of-band security update for this end-of-support platform. Look up the KB number in the vendor advisory. Treat it as a stopgap only, because Windows Server 2003 receives no regular security updates.
      • Restrict exposure: Limit TCP 80/443 to these hosts at the perimeter firewall to known source ranges, or block it entirely. If neither is possible, pull the host off the network until WebDAV is disabled.
      • Start a compromise assessment: On internet-exposed IIS 6.0 systems, preserve IIS logs, the running process list and local accounts. Then rotate service-account and local admin credentials from a known-clean system. Rebuild compromised hosts rather than cleaning them.
    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Move any remaining Server 2003 systems into an isolated legacy VLAN. Default-deny their egress to the internet and to server and client networks to break reverse shells and lateral movement.
      • Reverse proxy/WAF: Restrict a fronting proxy or WAF to the HTTP methods GET, HEAD and POST, and drop PROPFIND, PROPPATCH, MKCOL, LOCK and UNLOCK. Also reject requests whose If: header exceeds roughly 256 bytes or begins with If: <http://.
      • IPS signature: Enable a Suricata/Snort rule pairing http.method; content:"PROPFIND" with http.header; content:"If|3a| <http|3a|//" plus a length check (isdataat). Commercial rulesets (ET/Talos) ship ready-made signatures. Run them in blocking mode.
      • Host hardening: Deploy URLScan on IIS 6.0. In urlscan.ini, set UseAllowVerbs=1 and list only GET, HEAD and POST under [AllowVerbs]. Cap header sizes via [RequestLimits].
      • Least privilege: Run the application pool as Network Service or a dedicated non-admin account. This keeps code execution confined to the w3wp.exe context.
      • Strategic: Record migration to a supported Windows Server/IIS release as a dated treatment action in the risk register. Running Server 2003 is very hard to defend as an "appropriate measure" under NIS2 or ISO 27001 (A.8.8).
    3. Runbook step 3

      Detection rules

      • IIS logs (W3SVC, %SystemRoot%\system32\LogFiles\W3SVC*): Hunt for cs-method = PROPFIND, especially with status 500 or dropped connections. SPL: index=iis cs_method=PROPFIND | stats count by c_ip, cs_uri_stem, sc_status. The If header is not logged by default, so pair this with network visibility.
      • Network telemetry (Zeek/Suricata): Filter Zeek http.log for method == "PROPFIND" to IIS 6.0 targets. Inspect raw headers (http_header events) for If: <http://localhost/ followed by very long Unicode or letter strings. The public exploit uses this pattern with alphanumeric shellcode.
      • Process ancestry (Server 2003 Security log): Review Event ID 592 (process creation, the predecessor of 4688) for w3wp.exe or the WebDAV-hosting svchost.exe spawning cmd.exe, powershell.exe, cscript.exe, wscript.exe, net.exe or certutil.exe. Process-tracking audit must be enabled. Sysmon does not support Server 2003.
      • Crash indicators: Repeated unexpected w3wp.exe terminations in the System and Application logs (W3SVC worker-process failure warnings, application error events) point to failed exploit attempts. Correlate them with PROPFIND requests from the same source IP.
      • Egress anomalies: Alert on new outbound TCP sessions from the IIS host to unknown destinations, for example reverse shells on 4444 or 443, in firewall or NetFlow data. Sigma shape: src_host in legacy_iis AND direction=outbound AND dst_ip NOT IN allowlist.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    microsoftinternet_information_services
    • 6.0
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

      Base

      The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

      Entry at MITRE CWE-120

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    Reference tagged as exploitgithub.com (opens in a new tab)PoC (publicly reported)reported, not verified—
    Metasploit Framework (Pull Request)Metasploit PR #8162 (opens in a new tab)github.comPoC (publicly reported)reported, not verified—
    Exploit-DBEDB-ID 41738 (opens in a new tab)exploit-db.comPoC (publicly reported)reported, not verified—
    Exploit-DBEDB-ID 41992 (opens in a new tab)exploit-db.comPoC (publicly reported)reported, not verified—
    PoC-in-GitHub (nomi-sec)Penetration-Testing-Assessment-23-04-2026 (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    • exploit-db.com41992Exploit, x_refsource_EXPLOIT-DB, Exploit, Third-party advisory, Vulnerability database
    • securityfocus.com97127Vulnerability database, x_refsource_BID, Broken link, Third-party advisory, Vulnerability database
    • medium.com@iraklis/number-of-internet-facing-vulnerable-iis-6-0-to-cve-20…x_refsource_MISC, Exploit
    • github.comrapid7/metasploit-framework/pull/8162x_refsource_MISC, Issue tracking, Patch
    • github.comdanigargu/explodingcanx_refsource_MISC, Exploit
    • securitytracker.com1038168Vulnerability database, x_refsource_SECTRACK, Broken link, Third-party advisory, Vulnerability database
    • exploit-db.com41738Exploit, x_refsource_EXPLOIT-DB, Exploit, Third-party advisory, Vulnerability database
    • support.microsoft.comen-us/help/3197835/description-of-the-security-update-for-windo…x_refsource_CONFIRM, Broken link, Patch, Vendor advisory
    • 0patch.blogspot.com2017/03/0patching-immortal-cve-2017-7269.htmlx_refsource_MISC, Exploit, Third-party advisory
    • github.comedwardz246003/IIS_exploitx_refsource_MISC, Broken link, Third-party advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2017-7269government-resource, US government resource
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2017-7269
    <a href="https://intel.neosec.eu/en/cve/CVE-2017-7269"><img src="https://intel.neosec.eu/badge/cve/CVE-2017-7269.svg?lang=en" alt="CVE-2017-7269 – NEOSEC Intel" height="20"></a>