CVE-2025-24984: Microsoft Windows NTFS Information Disclosure Vulnerability

Published Mar 11, 2025
·
Updated

Insertion of sensitive information into log file in Windows NTFS allows an unauthorized attacker to disclose information with a physical attack.

Other sources

Microsoft Windows New Technology File System (NTFS) contains an insertion of sensitive Information into log file vulnerability that allows an unauthorized attacker to disclose information with a physical attack. An attacker who successfully exploited this vulnerability could potentially read portions of heap memory.

CISA

Windows NTFS Information Disclosure Vulnerability

Microsoft

Affected Software

81 affected componentsFixes available
Microsoft Windows 11=23H2
Microsoft Windows Server 2025
Microsoft Windows 11=22H2
Microsoft Windows Server 2016
Microsoft Windows Server 2019
Microsoft Windows Server 2012 R2
Microsoft Windows 11=24H2
Microsoft Windows Server 2022, 23H2 Edition
Microsoft Windows 11=24H2
Microsoft Windows Server 2012
Microsoft Windows 11=22H2
Microsoft Windows 11=23H2
Microsoft Windows Server 2016
Microsoft Windows Server 2019
Microsoft Windows Server 2025
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows Server 2022
Microsoft Windows Server 2022
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows 10=22H2
Microsoft Windows 10=22H2
Microsoft Windows 10=22H2
Microsoft Windows 10=1607
Microsoft Windows 10=1607
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Microsoft Windows 10
Microsoft Windows 10
Microsoft Windows
Microsoft Windows 10 1507<10.0.10240.20947
Microsoft Windows 10 1507<10.0.10240.20947
Microsoft Windows 10 1607<10.0.14393.7876
Microsoft Windows 10 1607<10.0.14393.7876
Microsoft Windows 10 1809<10.0.17763.7009
Microsoft Windows 10 1809<10.0.17763.7009
Microsoft Windows 10 21h2<10.0.19044.5608
Microsoft Windows 10 22h2<10.0.19045.5608
Microsoft Windows 11 22h2<10.0.22621.5039
Microsoft Windows 11 23h2<10.0.22631.5039
Microsoft Windows 11 24h2<10.0.26100.3403
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.7876
Microsoft Windows Server 2019<10.0.17763.7009
Microsoft Windows Server 2022<10.0.20348.3270
Microsoft Windows Server 2022 23h2<10.0.25398.1486
Microsoft Windows Server 2025<10.0.26100.3403
Microsoft Windows Server 2016<10.0.14393.7876
10.0.14393.7876
Microsoft Windows Server 2012 R2<6.3.9600.22470
6.3.9600.22470
Microsoft Windows Server 2012<6.2.9200.25368
6.2.9200.25368
Microsoft Windows Server 2012<6.2.9200.25368
6.2.9200.25368
Microsoft Windows 10=1607
10.0.14393.7876
Microsoft Windows Server 2016<10.0.14393.7876
10.0.14393.7876
Microsoft Windows 10<10.0.10240.20947
10.0.10240.20947
Microsoft Windows 10<10.0.10240.20947
10.0.10240.20947
Microsoft Windows Server 2012 R2<6.3.9600.22470
6.3.9600.22470
Microsoft Windows 10=1607
10.0.14393.7876
Microsoft Windows 11=24H2
10.0.26100.347610.0.26100.3403
Microsoft Windows 11=24H2
10.0.26100.347610.0.26100.3403
Microsoft Windows Server 2025<10.0.26100.3476, <10.0.26100.3403
10.0.26100.347610.0.26100.3403
Microsoft Windows Server 2025<10.0.26100.3476, <10.0.26100.3403
10.0.26100.347610.0.26100.3403
Microsoft Windows 11=23H2
10.0.22631.5039
Microsoft Windows Server 2022, 23H2 Edition<10.0.25398.1486
10.0.25398.1486
Microsoft Windows 10=22H2
10.0.19045.5608
Microsoft Windows 10=22H2
10.0.19045.5608
Microsoft Windows 10=22H2
10.0.19045.5608
Microsoft Windows 11=23H2
10.0.22631.5039
Microsoft Windows 11=22H2
10.0.22621.5039
Microsoft Windows 11=22H2
10.0.22621.5039
Microsoft Windows 10=21H2
10.0.19044.5608
Microsoft Windows 10=21H2
10.0.19044.5608
Microsoft Windows 10=21H2
10.0.19044.5608
Microsoft Windows Server 2022<10.0.20348.3328, <10.0.20348.3270
10.0.20348.332810.0.20348.3270
Microsoft Windows 10=1809
10.0.17763.7009
Microsoft Windows 10=1809
10.0.17763.7009
Microsoft Windows Server 2019<10.0.17763.7009
10.0.17763.7009
Microsoft Windows Server 2019<10.0.17763.7009
10.0.17763.7009
Microsoft Windows Server 2022<10.0.20348.3328, <10.0.20348.3270
10.0.20348.332810.0.20348.3270

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.14393.7876Patch KB5053594
  2. Upgrade

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

    Fixed in 6.3.9600.22470Patch KB5053887
  3. Upgrade

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

    Fixed in 6.2.9200.25368Patch KB5053886
  4. Upgrade

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

    Fixed in 10.0.10240.20947Patch KB5053618
  5. Upgrade

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

    Fixed in 10.0.26100.3476Fixed in 10.0.26100.3403Patch KB5053636
  6. Upgrade

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

    Fixed in 10.0.22631.5039Patch KB5053602
  7. Upgrade

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

    Fixed in 10.0.25398.1486Patch KB5053599
  8. Upgrade

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

    Fixed in 10.0.19045.5608Patch KB5053606
  9. Upgrade

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

    Fixed in 10.0.22621.5039Patch KB5053602
  10. Upgrade

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

    Fixed in 10.0.19044.5608Patch KB5053606
  11. Upgrade

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

    Fixed in 10.0.20348.3328Fixed in 10.0.20348.3270Patch KB5053638
  12. Upgrade

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

    Fixed in 10.0.17763.7009Patch KB5053596
  13. Upgrade

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

    Fixed in 10.0.20348.3328Patch KB5053638
  14. Upgrade

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

    Fixed in 10.0.20348.3270Patch KB5053638
  15. Upgrade

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

    Fixed in 10.0.26100.3476Patch KB5053636
  16. Upgrade

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

    Fixed in 10.0.26100.3403Patch KB5053636
  17. Compensating control

    Follow applicable BOD 22-01 guidance for cloud services.

  18. Compensating control

    Discontinue use of the affected product if mitigations are unavailable.

Event History

Mar 11, 2025
CVE Published
via CISA·12:00 AM
Known Exploited
via CISA·12:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Description
CVE Published
via MITRE·04:59 PM
Data Sourced
via MITRE·04:59 PM
DescriptionSeverity
Data Sourced
via NVD·05:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Mar 12, 2025
News Published
via The Register·01:24 AM
News Published
via The Register·01:29 AM
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-2025-24984?

CVE-2025-24984 is classified as a high severity vulnerability due to its potential for sensitive information disclosure.

2

How do I fix CVE-2025-24984?

To remediate CVE-2025-24984, apply the latest security patch provided by Microsoft for the affected Windows versions.

3

Which versions of Windows are affected by CVE-2025-24984?

CVE-2025-24984 affects multiple versions of Windows including Windows 10, Windows 11, and various Windows Server editions.

4

What type of attack does CVE-2025-24984 allow?

CVE-2025-24984 allows unauthorized attackers to disclose sensitive information through physical access to systems.

5

Can the CVE-2025-24984 vulnerability be exploited remotely?

No, CVE-2025-24984 requires physical access to the affected machine to exploit the vulnerability.

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