CVE-2024-43451

NTLM Hash Disclosure Spoofing Vulnerability

MEDIUM
6.5
CVSS Score
Published: November 12, 2024 at 05:53 PM UTC
Updated: June 17, 2026 at 07:51 AM UTC
16 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows Server 2025 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows Server 2025 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploitation
CISA KEV
Exploit prediction
EPSS 84%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score84.3%

EPSS (Exploit Prediction Scoring System) estimates a 84.3% chance this CVE is exploited in the wild within the next 30 days — higher than 100% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

Microsoft Windows contains an NTLMv2 hash spoofing vulnerability that could result in disclosing a user's NTLMv2 hash to an attacker via a file open operation. The attacker could then leverage this hash to impersonate that user.

Required Action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Ransomware Use
Unknown
Added to KEV
Nov 12, 2024
Remediation Due
Dec 3, 2024
692 days overdue

Description

NTLM Hash Disclosure Spoofing Vulnerability

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.10240.2082610.0.10240.0 ≤ v < 10.0.10240.2082610.0.10240.0
Affected range stops below 10.0.10240.20826, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.751510.0.14393.0 ≤ v < 10.0.14393.751510.0.14393.0
Affected range stops below 10.0.14393.7515, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.653210.0.17763.0 ≤ v < 10.0.17763.653210.0.17763.0
Affected range stops below 10.0.17763.6532, so it looks safe — our inference, not a vendor statement
v < 10.0.19044.513110.0.19043.0 ≤ v < 10.0.19044.513110.0.19043.0
Affected range stops below 10.0.19044.5131, so it looks safe — our inference, not a vendor statement
v < 10.0.19045.513110.0.19045.0 ≤ v < 10.0.19045.513110.0.19045.0
Affected range stops below 10.0.19045.5131, so it looks safe — our inference, not a vendor statement
v < 10.0.22621.446010.0.22621.0 ≤ v < 10.0.22621.446010.0.22621.0
Affected range stops below 10.0.22621.4460, so it looks safe — our inference, not a vendor statement
v < 10.0.22631.446010.0.22631.0 ≤ v < 10.0.22631.446010.0.22631.0
Affected range stops below 10.0.22631.4460, so it looks safe — our inference, not a vendor statement
v < 10.0.26100.231410.0.26100.0 ≤ v < 10.0.26100.231410.0.26100.0
Affected range stops below 10.0.26100.2314, so it looks safe — our inference, not a vendor statement
6.0.6003.0 ≤ v < 6.0.6003.229666.1.7601.0 ≤ v < 6.1.7601.274156.0.6003.06.1.7601.0r2 sp1sp2
Affected range stops below 6.0.6003.22966, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.7601.27415, so it looks safe — our inference, not a vendor statement
6.3.9600.0 ≤ v < 6.3.9600.222676.3.9600.0r2
Affected range stops below 6.3.9600.22267, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCActiveNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUMmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-73NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card