CVE-2025-24054: NTLM Hash Disclosure Spoofing Vulnerability

Overview

Severity
Medium (CVSS 6.5)
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
Category
Spoofing
Exploit Status
Not Exploited
Exploitation Likelihood
Less Likely
Patch Tuesday
2025-Mar
Released
2025-03-11
Last Updated
2025-04-25
EPSS Score
11.93% (percentile: 93.8%)
CISA KEV
Listed — due 2025-05-08

Description

External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network.

FAQ

According to the CVSS metric, user interaction is required (UI:R). What interaction would the user have to do? Minimal interaction with a malicious file by a user such as selecting (single-click), inspecting (right-click), or performing an action other than opening or executing the file could trigger this vulnerability.

Known Exploits (11)

  • Microsoft Windows NTLM Hash Disclosure Spoofing Vulnerability — added 2026-04-01T21:11:46Z
  • Microsoft Windows NTLM Hash Disclosure Spoofing Vulnerability — added 2025-12-10T05:41:26Z
  • Microsoft Windows NTLM Hash Disclosure Spoofing Vulnerability — added 2025-11-23T13:30:38Z
  • Microsoft Windows NTLM Hash Disclosure Spoofing Vulnerability — added 2025-08-13T08:16:29Z
  • Microsoft Windows NTLM Hash Disclosure Spoofing Vulnerability — added 2025-06-14T06:46:00Z
  • Microsoft Windows NTLM Hash Disclosure Spoofing Vulnerability — added 2025-05-19T19:53:11Z
  • Microsoft Windows NTLM Hash Disclosure Spoofing Vulnerability — added 2025-05-01T21:57:19Z
  • Microsoft Windows NTLM Hash Disclosure Spoofing Vulnerability — added 2025-04-27T06:50:48Z
  • Microsoft Windows NTLM Hash Disclosure Spoofing Vulnerability — added 2025-04-22T13:04:41Z
  • Microsoft Windows NTLM Hash Disclosure Spoofing Vulnerability — added 2025-04-18T11:17:48Z
  • Microsoft Windows NTLM Hash Disclosure Spoofing Vulnerability — added 2024-06-04T13:44:29Z

Detection & Weaponization (2 sources)

Maturity: Detection

  • Sigma rules: Suspicious Creation of .library-ms File — Potential CVE-2025-24054 Exploit
  • GitHub PoC: 8 repositories

Affected Products (33)

Windows

  • Windows 10 Version 1809 for 32-bit Systems
  • Windows 10 Version 1809 for x64-based Systems
  • Windows Server 2019
  • Windows Server 2019 (Server Core installation)
  • Windows Server 2022
  • Windows Server 2022 (Server Core installation)
  • Windows 10 Version 21H2 for 32-bit Systems
  • Windows 10 Version 21H2 for ARM64-based Systems
  • Windows 10 Version 21H2 for x64-based Systems
  • Windows Server 2025 (Server Core installation)
  • Windows 11 Version 23H2 for ARM64-based Systems
  • Windows 11 Version 23H2 for x64-based Systems
  • Windows Server 2022, 23H2 Edition (Server Core installation)
  • Windows 11 Version 24H2 for ARM64-based Systems
  • Windows 11 Version 24H2 for x64-based Systems
  • Windows Server 2025
  • Windows 10 for 32-bit Systems
  • Windows 10 for x64-based Systems
  • Windows 10 Version 1607 for 32-bit Systems
  • Windows 10 Version 1607 for x64-based Systems
  • Windows Server 2016
  • Windows Server 2016 (Server Core installation)

ESU

  • Windows 11 Version 22H2 for ARM64-based Systems
  • Windows 11 Version 22H2 for x64-based Systems
  • Windows 10 Version 22H2 for x64-based Systems
  • Windows 10 Version 22H2 for ARM64-based Systems
  • Windows 10 Version 22H2 for 32-bit Systems
  • Windows Server 2008 R2 for x64-based Systems Service Pack 1
  • Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
  • Windows Server 2012
  • Windows Server 2012 (Server Core installation)
  • Windows Server 2012 R2
  • Windows Server 2012 R2 (Server Core installation)

Security Updates (12)

Acknowledgments

Rintaro Koike with NTT Security Holdings, <a href="https://x.com/0x6rss">0x6rss</a>, <a href="http://hyp3rlinx.altervista.org">hyp3rlinx</a>, <a href="https://twitter.com/j00sean">j00sean</a>

Revision History

  • 2025-03-11: Information published.
  • 2025-03-18: Added an acknowledgement. This is an informational change only.
  • 2025-04-25: Added an acknowledgement. This is an informational change only.