Threats / Microsoft / CVE-2024-43451
CVE-2024-43451
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Windows vulnerability
Microsoft Windows NTLMv2 hash spoofing vulnerability allows attackers to disclose user authentication hashes via file operations, enabling user impersonation.
Verdict
Today item — known-exploited.
An attacker can trigger NTLMv2 hash disclosure through a file open operation, capture the hash, and use it to impersonate the affected user within the network, bypassing authentication controls.
CISA KEV Yes · 2024-11-125EPSS 0.81817 (verify live)6Exploit Public PoC7CVSS 6.53CISA SSVC Exploitation: active · Automatable: no · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
18 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-11-12).
Probability (EPSS)
EPSS 0.81817 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:F/RL:O/RC:C) · Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-73 CWE-73 — weakness family: Path traversal / file.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a file operation that triggers the target system to transmit its NTLMv2 hash to my controlled location.
Business
User authentication credentials are exposed to network-based capture and offline cracking attempts.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I intercept or receive the NTLMv2 hash and use it to authenticate as the legitimate user without knowing their password.
Business
Lateral movement and privilege escalation become possible as the attacker operates with legitimate user credentials.
3
Lateral reach — past segmentation narrative 3
Attacker
I access resources and systems that the impersonated user can reach, exfiltrating data or establishing persistence.
Business
Confidential data is compromised and attackers gain sustained access to critical systems and networks.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05