CVE-2017-7269
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBuffer 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBuffer overflow vulnerability in IIS 6.0 WebDAV's ScStoragePathFromUrl function on Windows Server 2003 R2. Exploitation occurs via a PROPFIND request containing an excessively long 'If: <http://...' header, enabling remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify IIS versionCheck the IIS version by running 'inetmgr' and looking at the version information, or check the file version of %SystemRoot%\System32\inetsrv\inetinfo.exeAffected if version is not 6.0 - only IIS 6.0 is affected
-
Confirm WebDAV is enabledOpen IIS Manager, expand the server node, click on 'WebDAV Authoring Rules' or check for the WebDAV component in IIS 6.0 Management Console under 'Web Service Extensions'Affected if WebDAV is enabled - the vulnerability only exists when WebDAV is active; if WebDAV is disabled, the server is not affected
-
Check WebDAV authoring rulesIn IIS Manager, examine the WebDAV Authoring Rules configuration to see if any rules allow anonymous or authenticated PROPFIND methodsAffected if WebDAV rules permit PROPFIND requests - the exploit uses PROPFIND method with malicious 'If:' headers
-
Assess network exposureDetermine if the IIS server is directly accessible via HTTP/HTTPS from untrusted networks, as the attack requires sending PROPFIND requests to the serverAffected if the server is exposed to untrusted network traffic - remote attackers must be able to send HTTP PROPFIND requests to exploit this flaw
The server is affected only if it runs IIS version 6.0 with WebDAV enabled and is network-accessible to attackers; if WebDAV is disabled, the system is not vulnerable to this CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable WebDAV service if not required, or migrate from end-of-life Windows Server 2003 R2 to a supported Windows Server version.
- Consultation12.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7269 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-7269 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data