Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-43451: CWE-73: External Control of File Name or Path in Microsoft Windows Server 2025

0
Medium
VulnerabilityCVE-2024-43451cvecve-2024-43451cwe-73
Published: Tue Nov 12 2024 (11/12/2024, 17:53:48 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Windows Server 2025

Description

NTLM Hash Disclosure Spoofing Vulnerability

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/28/2026, 06:29:00 UTC

Technical Analysis

CVE-2024-43451 is a vulnerability classified under CWE-73 (External Control of File Name or Path) affecting Microsoft Windows Server 2025, specifically version 10.0.26100.0. This vulnerability enables an attacker to manipulate file paths externally, leading to NTLM hash disclosure spoofing. NTLM (NT LAN Manager) hashes are used in Windows authentication protocols, and their disclosure can facilitate credential theft or relay attacks. The flaw does not require any privileges but does require user interaction, such as opening a malicious file or link, and can be exploited remotely over the network. The vulnerability impacts confidentiality by exposing sensitive authentication hashes but does not affect system integrity or availability. The CVSS 3.1 base score is 6.5, indicating a medium severity level, with an attack vector of network, low attack complexity, no privileges required, and user interaction needed. No known exploits have been reported in the wild, and no patches have been published yet, though the vulnerability is officially documented and reserved since August 2024. This vulnerability highlights risks in handling external file paths in Windows Server 2025, potentially allowing attackers to spoof NTLM hashes and gain unauthorized access or escalate privileges indirectly.

Potential Impact

The primary impact of CVE-2024-43451 is the potential disclosure of NTLM authentication hashes, which can be leveraged by attackers to impersonate users or conduct relay attacks, undermining the confidentiality of authentication credentials. This can lead to unauthorized access to sensitive systems and data, especially in environments relying heavily on NTLM authentication. Although integrity and availability are not directly affected, the compromise of authentication credentials can facilitate further attacks that may impact these aspects. Organizations running Windows Server 2025 in critical roles such as domain controllers, file servers, or application servers are particularly at risk. The vulnerability's requirement for user interaction and network accessibility broadens the attack surface, especially in environments with remote users or exposed services. The absence of known exploits currently limits immediate risk, but the medium severity score and potential for credential theft warrant proactive mitigation to prevent escalation and lateral movement within networks.

Mitigation Recommendations

1. Monitor official Microsoft channels closely for patches or security advisories addressing CVE-2024-43451 and apply updates promptly once available. 2. Implement strict network segmentation and limit exposure of Windows Server 2025 systems to untrusted networks to reduce attack surface. 3. Enforce strong user awareness training to minimize risky user interactions that could trigger exploitation, such as opening suspicious files or links. 4. Disable or restrict NTLM authentication where possible, transitioning to more secure authentication protocols like Kerberos to reduce reliance on vulnerable NTLM hashes. 5. Employ network-level protections such as SMB signing and encryption to mitigate interception or manipulation of authentication traffic. 6. Use endpoint detection and response (EDR) tools to monitor for unusual file path manipulations or suspicious authentication activities indicative of exploitation attempts. 7. Regularly audit and harden file system permissions to prevent unauthorized external control of file paths. 8. Consider deploying application whitelisting and restricting execution of untrusted code to limit exploitation vectors. These measures collectively reduce the likelihood and impact of exploitation beyond generic patching advice.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
microsoft
Date Reserved
2024-08-14T01:08:33.514Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68f7d9b4247d717aace26abc

Added to database: 10/21/2025, 7:06:28 PM

Last enriched: 2/28/2026, 6:29:00 AM

Last updated: 3/27/2026, 11:52:57 AM

Views: 115

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses