ExploitPublished
Microsoft - NTLM Hash Disclosure Spoofing (library-ms)
Source Exploit-DB RSS Feed
0
Mentioned vulnerabilities
Severity
MediumRated by Threat Radar
Data as of 11 Jun 2025, 21:11 UTC
What to do
AI-suggested
- Immediate application of any available Microsoft patches or updates addressing CVE-2025-24054 is critical. Even if no direct patch exists yet, monitor Microsoft’s security update guide closely for releases.
- Implement network segmentation to limit access to systems processing .library-ms files, reducing the attack surface for remote exploitation.
- Enforce strict network access controls and monitor for unusual access patterns to Windows file shares and library folders.
- Disable or restrict the use of NTLM authentication where possible, migrating to more secure protocols such as Kerberos.
- Employ multi-factor authentication (MFA) to reduce the impact of credential theft.
- Conduct regular credential hygiene practices, including frequent password changes and use of strong, unique passwords.
- Deploy endpoint detection and response (EDR) solutions to identify suspicious activities related to .library-ms file handling or NTLM hash extraction attempts.
- Educate IT and security teams about the specific nature of this exploit and the risks associated with NTLM hash disclosure.
- Use network intrusion detection systems (NIDS) with signatures or heuristics tuned to detect exploitation attempts leveraging this vulnerability.
- Restrict the execution of unauthorized scripts or binaries, including Perl scripts, on critical systems to hinder exploit deployment. These measures, combined with vigilant monitoring and incident response readiness, will help mitigate the risk posed by this vulnerability.
Description
Microsoft - NTLM Hash Disclosure Spoofing (library-ms)
Indicators of compromise
Exploit source code
# Exploit title: Microsoft - NTLM Hash Disclosure Spoofing (library-ms)
# Exploit Author: John Page (aka hyp3rlinx)
# x.com/hyp3rlinx
# ISR: ApparitionSec
Back in 2018, I reported a ".library-ms" File NTLM information disclosure vulnerability to MSRC and was told "it was not severe enough", that being said I post it anyways.
Seven years passed, until other researchers re-reported it.
Subsequently this security flaw was finally deemed important by Microsoft and it received CVE-2025-24054, for …References
Community reviews
Loading reviews…