Skip to main content
Mallory
MediumCISA KEVExploited in the wildPublic exploit

Windows NTLM Hash Disclosure via Malicious .url File

IdentifiersCVE-2024-43451CWE-73· External Control of File Name or…

CVE-2024-43451 is a Microsoft Windows NTLM hash disclosure spoofing vulnerability in the handling of Internet Shortcut (.url) files. The issue can cause Windows to initiate outbound SMB authentication to an attacker-controlled server when a user performs minimal interaction with a malicious file, including actions such as single-clicking, right-clicking, inspecting, dragging, deleting, or otherwise interacting with the file in Explorer without opening or executing it. Multiple reports in the provided content describe the flaw as exposing the victim’s NTLMv2 hash through crafted .url/network shortcut content and characterize it as a logical flaw in how Windows processes SMB paths referenced by such files. The vulnerability was patched by Microsoft in November 2024 and was reported as actively exploited in the wild, including campaigns targeting Ukraine and Colombia.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation discloses the victim user’s NTLMv2 hash to a remote attacker. This is an information disclosure issue that can directly enable credential theft workflows, including offline password cracking attempts, NTLM relay/pass-the-hash style abuse, account impersonation, and follow-on intrusion activity. Depending on the privileges of the affected account and the surrounding environment, the leaked credentials may support lateral movement, access to internal Windows resources, malware delivery, and broader compromise of enterprise systems.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by restricting or disabling NTLM where operationally feasible, blocking outbound SMB/NTLM authentication to untrusted networks, and monitoring for unexpected SMB authentication attempts to external hosts. Harden email and web filtering to block or quarantine malicious .url files and archives containing them. Limit user interaction with untrusted shortcut files, and implement detection for suspicious Explorer-triggered SMB connections and NTLM authentication events. Additional defensive measures noted in the supporting content for NTLM-related risk reduction include enabling message signing, implementing Extended Protection for Authentication where applicable, and accelerating migration away from NTLM to stronger authentication mechanisms.

Remediation

Patch, then assume compromise.

Apply Microsoft’s November 2024 security updates that address CVE-2024-43451 on all supported Windows systems. Prioritize patching endpoints that process email attachments, downloaded archives, or user-supplied shortcut files, especially in environments where NTLM remains enabled and outbound SMB is possible. Validate that legacy systems receiving Security Only updates, including older Windows Server versions referenced in the content, also receive the relevant cumulative/security fixes where applicable.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2008 R2operating_system
Microsoft CorporationWindows Server 2008 Sp2operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence13

Every observed campaign linking this CVE to a named adversary.

Associated malware6

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.