CVE-2025-21377

6.5 MEDIUM

📋 TL;DR

This vulnerability allows attackers to spoof NTLM hash disclosure, potentially enabling credential theft and lateral movement. It affects systems using NTLM authentication, particularly Windows environments. Organizations relying on NTLM for authentication are at risk.

💻 Affected Systems

Products:
  • Microsoft Windows
  • Systems using NTLM authentication
Versions: Specific versions not yet detailed in public advisory
Operating Systems: Windows Server, Windows Client versions
Default Config Vulnerable: ⚠️ Yes
Notes: Systems with NTLM authentication enabled are vulnerable. Kerberos-only environments may not be affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal NTLM hashes, perform pass-the-hash attacks, gain domain admin privileges, and compromise entire Active Directory environments.

🟠

Likely Case

Credential theft leading to lateral movement within networks, privilege escalation, and data exfiltration from compromised systems.

🟢

If Mitigated

Limited impact with proper network segmentation, NTLM restrictions, and monitoring in place.

🌐 Internet-Facing: MEDIUM - Requires NTLM authentication exposure to internet, which should be limited in modern environments.
🏢 Internal Only: HIGH - Most exploitation would occur within internal networks where NTLM is commonly used.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires network access and ability to intercept or manipulate NTLM authentication flows.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Microsoft Security Update Guide for specific KB numbers

Vendor Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21377

Restart Required: Yes

Instructions:

1. Apply latest Windows security updates from Microsoft Update. 2. Restart affected systems. 3. Verify patch installation via Windows Update history.

🔧 Temporary Workarounds

Disable NTLM Authentication

windows

Configure systems to use Kerberos authentication only where possible

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Lsa" -Name "RestrictSendingNTLMTraffic" -Value 2

Enable NTLM Auditing

windows

Monitor NTLM authentication attempts for suspicious activity

auditpol /set /subcategory:"Network Policy Server" /success:enable /failure:enable

🧯 If You Can't Patch

  • Implement network segmentation to isolate systems using NTLM
  • Deploy additional authentication controls like multi-factor authentication

🔍 How to Verify

Check if Vulnerable:

Check if NTLM authentication is enabled and systems are unpatched via Windows Update status

Check Version:

systeminfo | findstr /B /C:"OS Name" /C:"OS Version"

Verify Fix Applied:

Verify Windows Update history shows the relevant security update installed

📡 Detection & Monitoring

Log Indicators:

  • Unusual NTLM authentication patterns
  • Multiple failed NTLM attempts from single source
  • NTLM authentication from unexpected locations

Network Indicators:

  • Unusual NTLM traffic patterns
  • NTLM authentication to unexpected services
  • SMB or other protocol abuse for NTLM relay

SIEM Query:

source="windows-security" EventCode=4625 AuthenticationPackage=NTLM | stats count by src_ip

🔗 References

📤 Share & Export