# CVE-2017-7269: Microsoft Windows Server Buffer Overflow

> Remote attackers can execute arbitrary code on Windows Server 2003 via a buffer overflow in the IIS WebDAV service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-fj79-76j8-9vjm

## What is CVE-2017-7269?

CVE-2017-7269 is a critical memory corruption vulnerability in Microsoft Internet Information Services, published on 27 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2017-7269?

It affects 1 product.


Products: Microsoft Internet Information Services.

## How do I fix CVE-2017-7269?

No fix has been published for CVE-2017-7269 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2017-7269 being exploited?

Yes. Attackers have exploited CVE-2017-7269 in the wild since at least 3 Nov 2021.

Public exploit code:

- fixed msf module for cve-2017-7269 (github_poc): https://github.com/zcgonvh/cve-2017-7269
- iis6 exploit 2017 CVE-2017-7269 (github_poc): https://github.com/g0rx/iis6-exploit-2017-CVE-2017-7269
- CVE-2017-7269 回显PoC ,用于远程漏洞检测.. (github_poc): https://github.com/lcatro/CVE-2017-7269-Echo-PoC
- CVE-2017-7269 to webshell or shellcode loader (github_poc): https://github.com/zcgonvh/cve-2017-7269-tool
- An exploit for Microsoft IIS 6.0 CVE-2017-7269 (github_poc): https://github.com/eliuha/webdav_exploit
- https://github.com/Al1ex/CVE-2017-7269 (github_poc): https://github.com/Al1ex/CVE-2017-7269

## Other vulnerabilities in Microsoft Internet Information Services

- [CVE-2010-3972](https://insights.sbomify.com/CVE-2010-3972/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-4301](https://insights.sbomify.com/CVE-2008-4301/): Other in n/a (critical 10.0)
- [CVE-2007-2815](https://insights.sbomify.com/CVE-2007-2815/): The "hit-highlighting" functionality in webhits.dll in Microsoft Internet Information Services (IIS) Web Server 5.0 only uses Windows NT ACL (critical 10.0)
- [CVE-2003-0224](https://insights.sbomify.com/CVE-2003-0224/): Buffer overflow in ssinc.dll for Microsoft Internet Information Services (IIS) 5.0 allows local users to execute arbitrary code via a web pa (critical 10.0)
- [CVE-1999-0233](https://insights.sbomify.com/CVE-1999-0233/): IIS 1.0 allows users to execute arbitrary commands using .bat or .cmd files. (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7269 and fix it if it is affected.

What it is: CVE-2017-7269 is a critical memory corruption vulnerability in Microsoft Internet Information Services, published on 27 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-7269 in the wild since at least 3 Nov 2021.

Affected product: Microsoft Internet Information Services. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-7269/ (Markdown: https://insights.sbomify.com/CVE-2017-7269/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7269
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7269
- OSV: https://osv.dev/vulnerability/CVE-2017-7269

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-7269/
Summaries are generated and may contain mistakes; the official description above is the record.