# CVE-2015-1635: Microsoft HTTP.sys Remote Code Execution

> Remote attackers can execute arbitrary code on Windows systems via crafted HTTP requests to the HTTP.sys kernel driver.

- **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 10 Feb 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2015
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-p8wc-6g47-vh8j

## What is CVE-2015-1635?

CVE-2015-1635 is a critical code injection vulnerability in Microsoft Windows 7, published on 14 Apr 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HTTP.sys in Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8, Windows 8.1, and Windows Server 2012 Gold and R2 allows remote attackers to execute arbitrary code via crafted HTTP requests, aka "HTTP.sys Remote Code Execution Vulnerability."

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2015-1635?

It affects 5 products.


Products: Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012.

## How do I fix CVE-2015-1635?

No fix has been published for CVE-2015-1635 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 10 Aug 2022.

## Is CVE-2015-1635 being exploited?

Yes. Attackers have exploited CVE-2015-1635 in the wild since at least 10 Feb 2022.

Public exploit code:

- Concurrent network scanner for CVE-2015-1635 (github_poc): https://github.com/technion/erlvulnscan
- MS15-034 HTTP.sys 远程执行代码检测脚本（MS15-034 HTTP.sys remote execution code poc script） (github_poc): https://github.com/aedoo/CVE-2015-1635-POC
- CVE-2015-1635,MS15-034 (github_poc): https://github.com/Zx7ffa4512-Python/Project-CVE-2015-1635
- https://github.com/h3x0v3rl0rd/CVE-2015-1635-POC (github_poc): https://github.com/h3x0v3rl0rd/CVE-2015-1635-POC
- CVE-2015-1635 (github_poc): https://github.com/bongbongco/MS15-034
- CVE-2015-1635-POC，指定IP与端口验证HTTP.sys漏洞是否存在 (github_poc): https://github.com/w01ke/CVE-2015-1635-POC

## Other vulnerabilities in Microsoft Windows 7

- [CVE-2015-2360](https://insights.sbomify.com/CVE-2015-2360/): Microsoft Win32k Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6324](https://insights.sbomify.com/CVE-2014-6324/): Microsoft Kerberos Key Distribution Center (KDC) Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6332](https://insights.sbomify.com/CVE-2014-6332/): Microsoft Windows Object Linking & Embedding (OLE) Automation Array Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2014-4148](https://insights.sbomify.com/CVE-2014-4148/): Microsoft Windows Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2014-1812](https://insights.sbomify.com/CVE-2014-1812/): Microsoft Windows Group Policy Preferences Password Privilege Escalation (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1635 and fix it if it is affected.

What it is: CVE-2015-1635 is a critical code injection vulnerability in Microsoft Windows 7, published on 14 Apr 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2015-1635 in the wild since at least 10 Feb 2022.

Affected product: Microsoft Windows 7. 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-2015-1635/ (Markdown: https://insights.sbomify.com/CVE-2015-1635/index.md)
```

## Sources

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

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