# CVE-2022-21907: HTTP Protocol Stack Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code on Windows systems by exploiting the HTTP Protocol Stack, requiring immediate patching.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jan 2022
- **Updated:** 2 Jan 2025
- **Also known as:** GHSA-cgqq-62rg-6vmf

## What is CVE-2022-21907?

CVE-2022-21907 is a critical code injection vulnerability in Microsoft Windows 10, published on 11 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HTTP Protocol Stack Remote Code Execution Vulnerability

## Which versions are affected by CVE-2022-21907?

It affects 4 products.


Products: Microsoft Windows 10, Microsoft Windows 11, Microsoft Windows Server, Microsoft Windows Server 2019.

## How do I fix CVE-2022-21907?

No fix has been published for CVE-2022-21907 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-21907 being exploited?

There is no known exploitation of CVE-2022-21907 in the wild and no public exploit code.

Public exploit code:

- HTTP Protocol Stack Remote Code Execution Vulnerability CVE-2022-21907 (github_poc): https://github.com/ZZ-SOCMAP/CVE-2022-21907
- A REAL DoS exploit for CVE-2022-21907 (github_poc): https://github.com/polakow/CVE-2022-21907
- Proof of concept of CVE-2022-21907 Double Free in http.sys driver, triggering a kernel crash on IIS servers (github_poc): https://github.com/p0dalirius/CVE-2022-21907-http.sys
- CVE-2022-21907 Vulnerability PoC (github_poc): https://github.com/michelep/CVE-2022-21907-Vulnerability-PoC
- CVE-2022-21907: detection, protection, exploitation and demonstration. Exploitation: Powershell, Python, Ruby, NMAP and Metasploit. Detection and protection: Powershell. Demonstration: Youtube. (github_poc): https://github.com/mauricelambert/CVE-2022-21907
- POC for CVE-2022-21907: HTTP Protocol Stack Remote Code Execution Vulnerability. (github_poc): https://github.com/Malwareman007/CVE-2022-21907

## Other vulnerabilities in Microsoft Windows 10

- [CVE-2015-2426](https://insights.sbomify.com/CVE-2015-2426/): Microsoft Windows Adobe Type Manager Library Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2015-1769](https://insights.sbomify.com/CVE-2015-1769/): Microsoft Windows Mount Manager Privilege Escalation (medium 6.6, exploited in the wild)
- [CVE-2020-1467](https://insights.sbomify.com/CVE-2020-1467/): Windows Hard Link Elevation of Privilege Vulnerability (critical 10.0)
- [CVE-2021-26424](https://insights.sbomify.com/CVE-2021-26424/): Windows TCP/IP Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2021-28476](https://insights.sbomify.com/CVE-2021-28476/): Windows Hyper-V Remote Code Execution Vulnerability (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-21907 and fix it if it is affected.

What it is: CVE-2022-21907 is a critical code injection vulnerability in Microsoft Windows 10, published on 11 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-21907 in the wild and no public exploit code.

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

## Sources

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

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