Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2022-21907 — Vulnerability in HTTP Protocol Stack Enabling Remote Code Execution and Potential System Crash. | Kitploit
Tools/GitHubGitHub/kamal-marouane/cve-2022-21907
Vulnerability AnalysisExploitationPenetration TestingLearning & EducationLabs & Practice
GitHubkamal-marouane/cve-2022-21907

CVE-2022-21907

Vulnerability in HTTP Protocol Stack Enabling Remote Code Execution and Potential System Crash.

View Repository
1582 years agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2022-21907

Vulnerability in HTTP Protocol Stack Enabling Remote Code Execution and Potential System Crash.

Table of Contents

  • CVE-2022-21907
    • Description
    • Environment
      • Victim Machine Configuration
      • Attacker Machine Configuration
    • Exploit
    • Proof of Concept
    • References

Description

CVE-2022-21907 is a vulnerability in the HTTP Protocol Stack (http.sys) of Windows 10 that could be exploited by an attacker by sending a specially crafted packet to a targeted server utilizing the HTTP Protocol Stack to process packets. This can lead to a denial of service (DDoS) attack, where the server becomes unresponsive or crashes.

The exploitation of this flaw could be used to disrupt services and take a Windows 10 version 2004 machine offline without the need for authentication or user interaction.

Environment

First of all, you must have some free space in your hard disk in order to test this vulnerability (you can adjust memory allocation and also disk allocation after the installation of the VMs).

To begin testing this vulnerability, install Vagrant and VirtualBox using these links:

  • Vagrant Installation
  • VirtualBox Installation

Verify that the VBoxManage command is functional by entering it in CMD or PowerShell. If you receive an error such as:

"The term 'VBoxManage' is not recognized as the name of a cmdlet..."

Then ensure the VirtualBox path (e.g., C:\Program Files\Oracle\VirtualBox) is added to the System Environment Variables. Next, run the following command:

VBoxManage natnetwork add --netname MyCustomisedNet --network "192.168.100.0/24" --enable --dhcp on

Clone the following repository to obtain the necessary Vagrant files:

git clone https://github.com/kamal-marouane/CVE-2022-21907.git

Victim Machine Configuration

After Cloning the repo, enter to the Victim Machine directory on your machine by executing the following commands:

cd CVE-2022-21907/Victim Machine

In this folder you can find the Vagranfile, all you have to do is to execute :

vagrant up

wait-for
And wait for the box to be downloaded and added. It takes a lot of time seeing that its size is around 5 GB (the above image is only representative). After the installation ends, you can go to your VirtualBox and then see that MyWindowsVul was added and running.

first

Click on Show and you can see that your Victim Machine is Running

Screenshot-2023-12-10-013708

Attacker Machine Configuration

Now let's configure the attacker machine, you have now to access to the Attacker Machine :

cd ../Victim Machine

In this folder you can find the Vagranfile, all you have to do is to go back to your machinea and execute :

vagrant up

Wait for the box to be downloaded and added and then the machine will run, Click on Show then you will see the Attacker machine running.

4

Now the Machines are configured and ready to be used! These are the username and password to access the Attacker Machine :

username : attacker
password : att

image

Exploit

To exploit the Vulnerability, please follow carefully the following steps:

1 - open the running VMs :

Screenshot-2023-12-10-040604

2 - In the Victim Machine, open cmd and type ipconfig to find the IPv4 address set earlier. :

ipconfig

Then you will be able to observe the IPv4 address that was established using the VBoxManage command as mentioned above.

third

Save the IPv4 Address you got for later use.

Attention!! : The IP address on your virtual machine may differ from the one I have. Ensure that you use the IP address obtained after executing the ipconfig command (Note that the default GateAway must be 192.168.100.1 which we have already created using VBoxManage command, so your IP address in the Victim Machine should be in this form : 192.168.100.X).

3 - On the Kali Linux machine, navigate to the exploit directory and run the exploit script :

cd CVE-2022-21907-Exploit

4 - Execute the python script in the Attacker Machine to crash the Victim Machine :

python3 CVE-2022-21907-exploit.py -i VICTIM_MACHINE_IP

Here you have to replace VICTIM_MACHINE_IP by the address obtained in the Victim Machine.

5 - Congrtatulations!!! The Victim Machine is CRASHED :/

Proof of Concept

After Following all the steps mentioned in the Exploit section, the Victim Machine will be crashed.

exploit

References

  • https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-21907
  • https://piffd0s.medium.com/patch-diffing-cve-2022-21907-b739f4108eee
  • https://www.fortinet.com/blog/threat-research/analysis-of-microsoft-cve-2022-21907
  • https://crashtest-security.com/cve-2022-21907-http-vulnerability/
  • https://www.zerodayinitiative.com/blog/2021/5/17/cve-2021-31166-a-wormable-code-execution-bug-in-httpsys

Should you encounter any issues or require clarification on any of the steps, please don't hesitate to reach out via email for assistance :

[email protected]

Download Tool