CVE-2024-43451: Microsoft Windows NTLMv2 Hash Disclosure Spoofing Vulnerability

Published Nov 12, 2024
·
Updated

Microsoft Windows contains an NTLMv2 hash spoofing vulnerability that could result in disclosing a user's NTLMv2 hash to an attacker via a file open operation. The attacker could then leverage this hash to impersonate that user.

Other sources

NTLM Hash Disclosure Spoofing Vulnerability

Microsoft

Affected Software

70 affected componentsFixes available
Microsoft Windows Server 2025
Microsoft Windows Server 2025
Microsoft Windows Server 2012
Microsoft Windows Server 2012
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows
Microsoft Windows 10 1507<10.0.10240.20826
Microsoft Windows 10 1507<10.0.10240.20826
Microsoft Windows 10 1607<10.0.14393.7515
Microsoft Windows 10 1607<10.0.14393.7515
Microsoft Windows 10 1809<10.0.17763.6532
Microsoft Windows 10 1809<10.0.17763.6532
Microsoft Windows 10 21h2<10.0.19044.5131
Microsoft Windows 10 21h2<10.0.19044.5131
Microsoft Windows 10 21h2<10.0.19044.5131
Microsoft Windows 10 22h2<10.0.19045.5131
Microsoft Windows 10 22h2<10.0.19045.5131
Microsoft Windows 10 22h2<10.0.19045.5131
Microsoft Windows 11 22h2<10.0.22621.4460
Microsoft Windows 11 22h2<10.0.22621.4460
Microsoft Windows 11 23h2<10.0.22631.4460
Microsoft Windows 11 23h2<10.0.22631.4460
Microsoft Windows 11 24h2<10.0.26100.2314
Microsoft Windows 11 24h2<10.0.26100.2314
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=r2-sp1
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.7515
Microsoft Windows Server 2019<10.0.17763.6532
Microsoft Windows Server 2022<10.0.20348.2849
Microsoft Windows Server 2022 23h2<10.0.25398.1251
Microsoft Windows Server 2025<10.0.26100.2314
Microsoft Windows 10=1809
10.0.17763.6532
Microsoft Windows Server 2025<10.0.26100.2314, <10.0.26100.2240
10.0.26100.231410.0.26100.2240
Microsoft Windows Server 2008<6.0.6003.22966, <1.001
6.0.6003.229661.001
Microsoft Windows Server 2008 R2<6.1.7601.27415, <1.001
6.1.7601.274151.001
Microsoft Windows Server 2012 R2<6.3.9600.22267, <1.001
6.3.9600.222671.001
Microsoft Windows 10=1809
10.0.17763.6532
Microsoft Windows Server 2008 R2<6.1.7601.27415, <1.001
6.1.7601.274151.001
Microsoft Windows Server 2012 R2<6.3.9600.22267, <1.001
6.3.9600.222671.001
Microsoft Windows Server 2008<6.0.6003.22966, <1.001
6.0.6003.229661.001
Microsoft Windows Server 2025<10.0.26100.2314, <10.0.26100.2240
10.0.26100.231410.0.26100.2240
Microsoft Windows Server 2016<10.0.14393.7515
10.0.14393.7515
Microsoft Windows Server 2008<6.0.6003.22966, <1.001
6.0.6003.229661.001
Microsoft Windows Server 2008<6.0.6003.22966, <1.001
6.0.6003.229661.001
Microsoft Windows 10=1607
10.0.14393.7515
Microsoft Windows Server 2016<10.0.14393.7515
10.0.14393.7515
Microsoft Windows 10<10.0.10240.20826
10.0.10240.20826
Microsoft Windows 10=1607
10.0.14393.7515
Microsoft Windows 11=24H2
10.0.26100.231410.0.26100.2240
Microsoft Windows 11=23H2
10.0.22631.4460
Microsoft Windows 11=24H2
10.0.26100.231410.0.26100.2240
Microsoft Windows 10<10.0.10240.20826
10.0.10240.20826
Microsoft Windows 11=23H2
10.0.22631.4460
Microsoft Windows Server 2022, 23H2 Edition<10.0.25398.1251
10.0.25398.1251
Microsoft Windows 10=22H2
10.0.19045.5131
Microsoft Windows 10=22H2
10.0.19045.5131
Microsoft Windows 10=22H2
10.0.19045.5131
Microsoft Windows 11=22H2
10.0.22621.4460
Microsoft Windows 11=22H2
10.0.22621.4460
Microsoft Windows 10=21H2
10.0.19044.5131
Microsoft Windows Server 2022<10.0.20348.2849, <10.0.20348.2819
10.0.20348.284910.0.20348.2819
Microsoft Windows Server 2019<10.0.17763.6532
10.0.17763.6532
Microsoft Windows 10=21H2
10.0.19044.5131
Microsoft Windows Server 2019<10.0.17763.6532
10.0.17763.6532
Microsoft Windows 10=21H2
10.0.19044.5131
Microsoft Windows Server 2022<10.0.20348.2849, <10.0.20348.2819
10.0.20348.284910.0.20348.2819

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.6532Patch KB5046615
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.0.6003.22966Fixed in 1.001Patch KB5046630
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.2314Fixed in 10.0.26100.2240Patch KB5046696
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.1.7601.27415Fixed in 1.001Patch KB5046630
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.22267Fixed in 1.001Patch KB5046630
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.7515Patch KB5046612
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.10240.20826Patch KB5046665
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22631.4460Patch KB5046633
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.25398.1251Patch KB5046618
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19045.5131Patch KB5046613
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22621.4460Patch KB5046633
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.2849Fixed in 10.0.20348.2819Patch KB5046698
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.5131Patch KB5046613

Event History

Nov 12, 2024
CVE Published
via CISA·12:00 AM
Known Exploited
via CISA·12:00 AM
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
Description
CVE Published
via MITRE·05:53 PM
Data Sourced
via MITRE·05:53 PM
DescriptionSeverity
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Nov 13, 2024
News Published
via The Register·01:29 AM
News Published
via The Register·01:32 AM
News Published
via BleepingComputer·09:33 PM
News Published
via BleepingComputer·09:33 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-43451?

CVE-2024-43451 has a high severity rating due to the potential for NTLMv2 hash disclosure that can lead to user impersonation.

2

How do I fix CVE-2024-43451?

To mitigate CVE-2024-43451, apply the latest security patches provided by Microsoft for the affected Windows versions.

3

Which versions of Windows are affected by CVE-2024-43451?

CVE-2024-43451 affects various Windows versions including Windows 10 (all supported versions), Windows Server 2019, Windows 11, and Windows Server 2022.

4

How can an attacker exploit CVE-2024-43451?

An attacker can exploit CVE-2024-43451 by tricking users into performing file operations that inadvertently disclose their NTLMv2 password hashes.

5

Is there a workaround for CVE-2024-43451?

While the recommended solution is to apply updates, if immediate patching is not possible, limiting access to vulnerable file operations may serve as a temporary workaround.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203