Skip to content
Server Security Center
KEVmedium6.5

CVE-2024-43451: Microsoft Windows NTLMv2 Hash Disclosure Spoofing

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2024-11-12.

CVSS v3.1 (CVE record)
6.5
medium
EPSS (exploit probability, 30 days)
84%
higher than 99.7% of all CVEs
Added to CISA KEV
2024-11-12
US federal due date 2024-12-03
Automatable (CISA SSVC)
no
technical impact: partial

CVE-2024-43451 explained

CVE-2024-43451 is an NTLMv2 hash disclosure spoofing vulnerability in Microsoft Windows. A file open operation can disclose a user's NTLMv2 hash to an attacker, who can then use it to impersonate that user. CISA lists it as known to be exploited, so affected systems should be patched promptly.

Impact

An unauthenticated attacker over the network can obtain a user's NTLMv2 hash and use it to impersonate that user. User interaction is required, as the disclosure occurs through a file open operation. The direct impact is high confidentiality loss, with no direct integrity or availability impact. CISA rates it as not automatable with partial technical impact, but attackers are known to exploit it.

Who is affected

The CVE record lists Windows 10 Version 1809, 21H2 and 22H2, Windows 11 version 22H2, 22H3 and 23H2, and Windows Server 2019, 2022, 2022 23H2 Edition (Server Core) and 2025. Fixed builds include 10.0.17763.6532 (Windows 10 1809, Server 2019), 10.0.19044.5131 (Windows 10 21H2), 10.0.19045.5131 (Windows 10 22H2), 10.0.22621.4460 (Windows 11 22H2), 10.0.22631.4460 (Windows 11 22H3/23H2), 10.0.20348.2849 (Server 2022), 10.0.25398.1251 (Server 2022 23H2 Server Core) and 10.0.26100.2314 (Server 2025). The page lists further products.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.2314
    Fixed in
    • 10.0.26100.2314
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.2314
    Fixed in
    • 10.0.26100.2314
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.6532
    Fixed in
    • 10.0.17763.6532
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.6532
    Fixed in
    • 10.0.17763.6532
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.6532
    Fixed in
    • 10.0.17763.6532
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.2849
    Fixed in
    • 10.0.20348.2849
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.5131
    Fixed in
    • 10.0.19044.5131
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.4460
    Fixed in
    • 10.0.22621.4460
  • Microsoft Windows 10 Version 22H2x64, ARM64, 32-bit
    Affected
    • < 10.0.19045.5131
    Fixed in
    • 10.0.19045.5131
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.4460
    Fixed in
    • 10.0.22631.4460
Show 13 more products
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.4460
    Fixed in
    • 10.0.22631.4460
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1251
    Fixed in
    • 10.0.25398.1251
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.2314
    Fixed in
    • 10.0.26100.2314
  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.20826
    Fixed in
    • 10.0.10240.20826
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.7515
    Fixed in
    • 10.0.14393.7515
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.7515
    Fixed in
    • 10.0.14393.7515
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.7515
    Fixed in
    • 10.0.14393.7515
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.22966
    Fixed in
    • 6.0.6003.22966
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.22966
    Fixed in
    • 6.0.6003.22966
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27415
    Fixed in
    • 6.1.7601.27415
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27415
    Fixed in
    • 6.1.7601.27415
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22267
    Fixed in
    • 6.3.9600.22267
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22267
    Fixed in
    • 6.3.9600.22267

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows Server 2025: 10.0.26100.2314
    • Microsoft Windows Server 2025 (Server Core installation): 10.0.26100.2314
    • Microsoft Windows 10 Version 1809: 10.0.17763.6532
    • Microsoft Windows Server 2019: 10.0.17763.6532
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.6532
    • Microsoft Windows Server 2022: 10.0.20348.2849
    Fixed versions for 17 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43451
  • CISA's deadline for US federal agencies: 2024-12-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each affected system to the fixed build listed for its Windows version.
  2. Prioritize patching because CISA lists this vulnerability as known to be exploited.
  3. Follow the Microsoft advisory and apply any mitigations it describes where updates cannot be installed immediately.
  4. Warn users not to open files from untrusted or unexpected sources.
  5. Review accounts for signs of impersonation or unusual NTLM authentication activity.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Partial – limited control or information

Weakness: CWE-73 External Control of File Name or Path

Questions about CVE-2024-43451

Is CVE-2024-43451 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-11-12, with a US federal due date of 2024-12-03. Ransomware use is listed as unknown.
Does exploitation require user action?
Yes. The user must interact, as the hash is disclosed through a file open operation. No privileges are required for the attacker.
What can an attacker do with the disclosed hash?
According to the description, the attacker can use the user's NTLMv2 hash to impersonate that user.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.