CriticalCVE-2025-24984

    Windows NTFS Information Disclosure Vulnerability (CVE-2025-24984)

    Published In CISA KEV since Sources: pwn.watch, CVE.org, Msrc Update Guide

    What is affected, what to do

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

    The vulnerability is being actively exploited; treat it as a priority. Update Microsoft Windows 10 Version 1507 to version 10.0.10240.20947, Microsoft Windows 10 Version 1607 to version 10.0.14393.7876, Microsoft Windows 10 Version 1809 to version 10.0.17763.7009. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Microsoft Windows 10 Version 1507 lt 10.0.10240.0..10.0.10240.20947
    • Microsoft Windows 10 Version 1607 lt 10.0.14393.0..10.0.14393.7876
    • Microsoft Windows 10 Version 1809 lt 10.0.17763.0..10.0.17763.7009
    • Microsoft Windows 10 Version 21H2 lt 10.0.19044.0..10.0.19044.5608
    • Microsoft Windows 10 Version 22H2 lt 10.0.19045.0..10.0.19045.5608
    • Microsoft Windows 11 version 22H2 lt 10.0.22621.0..10.0.22621.5039
    • Microsoft Windows 11 version 22H3 lt 10.0.22631.0..10.0.22631.5039
    • Microsoft Windows 11 Version 23H2 lt 10.0.22631.0..10.0.22631.5039
    • Microsoft Windows 11 Version 24H2 lt 10.0.26100.0..10.0.26100.3476
    • Microsoft Windows Server 2012 lt 6.2.9200.0..6.2.9200.25368
    • Microsoft Windows Server 2012 (Server Core installation) lt 6.2.9200.0..6.2.9200.25368
    • Microsoft Windows Server 2012 R2 lt 6.3.9600.0..6.3.9600.22470
    • Microsoft Windows Server 2012 R2 (Server Core installation) lt 6.3.9600.0..6.3.9600.22470
    • Microsoft Windows Server 2016 lt 10.0.14393.0..10.0.14393.7876
    • Microsoft Windows Server 2016 (Server Core installation) lt 10.0.14393.0..10.0.14393.7876
    • Microsoft Windows Server 2019 lt 10.0.17763.0..10.0.17763.7009
    • Microsoft Windows Server 2019 (Server Core installation) lt 10.0.17763.0..10.0.17763.7009
    • Microsoft Windows Server 2022 lt 10.0.20348.0..10.0.20348.3328
    • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) lt 10.0.25398.0..10.0.25398.1486
    • Microsoft Windows Server 2025 lt 10.0.26100.0..10.0.26100.3476
    • Microsoft Windows Server 2025 (Server Core installation) lt 10.0.26100.0..10.0.26100.3476
    Fixed in
    • Microsoft Windows 10 Version 1507 10.0.10240.20947
    • Microsoft Windows 10 Version 1607 10.0.14393.7876
    • Microsoft Windows 10 Version 1809 10.0.17763.7009
    • Microsoft Windows 10 Version 21H2 10.0.19044.5608
    • Microsoft Windows 10 Version 22H2 10.0.19045.5608
    • Microsoft Windows 11 version 22H2 10.0.22621.5039
    • Microsoft Windows 11 version 22H3 10.0.22631.5039
    • Microsoft Windows 11 Version 23H2 10.0.22631.5039
    • Microsoft Windows 11 Version 24H2 10.0.26100.3476
    • Microsoft Windows Server 2012 6.2.9200.25368
    • Microsoft Windows Server 2012 (Server Core installation) 6.2.9200.25368
    • Microsoft Windows Server 2012 R2 6.3.9600.22470
    • Microsoft Windows Server 2012 R2 (Server Core installation) 6.3.9600.22470
    • Microsoft Windows Server 2016 10.0.14393.7876
    • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.7876
    • Microsoft Windows Server 2019 10.0.17763.7009
    • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.7009
    • Microsoft Windows Server 2022 10.0.20348.3328
    • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.1486
    • Microsoft Windows Server 2025 10.0.26100.3476
    • Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.3476

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    4.6

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    4.6

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: pwn.watch, CVE.org, Msrc Update Guide

    2.0 %

    EPSS score

    Moderate — model estimates 1-10% exploitation likelihood.

    Source: FIRST EPSS, percentile 80.6

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    183.10 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    4.6 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    4.6
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    2.0 %
    Moderate — model estimates 1-10% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    80.6
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-532

    Response and mitigation

    Why act now?

    Prioritisation rationale

    Exploitation requires physical access, but no authentication or user interaction. Impact is limited to confidentiality: heap memory contents can be disclosed, with no effect on integrity or availability. CISA added it alongside other NTFS and Fast FAT flaws fixed in the same Patch Tuesday, which points to targeted use via crafted removable media, possibly as one link in an attack chain. There is no known ransomware use, and exploitation likelihood is moderate. For most organisations this is a standard but mandatory fix in the next maintenance window. Escalate it for KRITIS operators with publicly accessible terminals, OT clients or a large mobile fleet.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Deploy the March 2025 Patch Tuesday cumulative update. Target builds: Windows 10 1507 → 10.0.10240.20947, 1607 → 10.0.14393.7876, 1809 → 10.0.17763.7009, 21H2/22H2 → 10.0.19044.5608 / 10.0.19045.5608, Windows 11 22H2 → 10.0.22621.5039, 23H2 → 10.0.22631.5039. Look up the KB numbers in the Microsoft Security Update Guide entry for CVE-2025-24984.
      • Verify patch compliance from inventory (Intune, SCCM/MECM, WSUS reporting) by querying for OS build below the target build. Check server SKUs sharing the 1607/1809 codebase against the vendor advisory.
      • Patch physically exposed assets first: laptops and travel devices, kiosks and reception PCs, shop-floor and HMI clients, unattended machines in training and meeting rooms.
      • Until patched, block removable storage on exposed systems via GPO ("All Removable Storage classes: Deny all access") or MDE Device Control.
      • Review read access to event logs. Minimise membership of "Event Log Readers" and local admin rights, because the leaked heap memory ends up in log data.

    2. Runbook step 2

      Mitigation layers

      • Physical security: Lock or UEFI-disable USB ports on kiosk and OT clients. Set a UEFI password and disable external boot. Enforce physical access control in line with ISO 27001 Annex A 7.x.
      • Device control: Restrict device installation via GPO ("Prevent installation of devices not described by other policy settings"). Maintain an allowlist of hardware/instance IDs for approved, encrypted corporate USB drives.
      • Disk encryption: Use BitLocker with pre-boot authentication (TPM+PIN) on mobile devices. This sharply reduces the attack surface for stolen or unattended hardware.
      • Treat log data as sensitive: Apply restrictive access to forwarded System/NTFS events in the SIEM. Limit raw-log access to the SOC role and align retention with data classification.
      • Least privilege: Allow only standard users to log on interactively to kiosk and shared systems. Without admin rights, reading protected logs becomes much harder.

    3. Runbook step 3

      Detection rules

      • Removable media attach: Monitor Security Event ID 6416 (requires "Audit PnP Activity") and Microsoft-Windows-Partition/Diagnostic EID 1006. Correlate the device identifiers against the USB allowlist.
      • MDE/KQL: DeviceEvents | where ActionType in ("UsbDriveMounted","PnpDeviceConnected") | where DeviceName in (exposed_assets). Prioritise hits outside business hours or on kiosk systems.
      • NTFS anomalies: Watch the System log, provider Ntfs, EIDs 55 and 98 (volume integrity/corruption), shortly after a removable volume mounts. This pattern suggests a crafted filesystem image. Sigma shape: logsource: windows/system, selection: Provider_Name: Ntfs, EventID: [55, 98], correlated with 6416 within 5 minutes.
      • Log-file access: Alert on object access auditing (EID 4663) on %SystemRoot%\System32\winevt\Logs\*.evtx by non-SOC accounts. Also alert on wevtutil.exe epl/qe run by standard users (Sysmon EID 1).
      • Physical indicators: Correlate lost/unattended device reports with subsequent console logons (EID 4624, Logon Type 2). Treat any recovered, unpatched device as potentially compromised.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

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

    Source: pwn.watch, NVD (NIST), Microsoft Security Update Guide, cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    MicrosoftWindows 10 Version 1507
    • 10.0.10240.0 – < 10.0.10240.20947
    • 10.0.10240.20947
    MicrosoftWindows 10 Version 1607
    • 10.0.14393.0 – < 10.0.14393.7876
    • 10.0.14393.7876
    MicrosoftWindows 10 Version 1809
    • 10.0.17763.0 – < 10.0.17763.7009
    • 10.0.17763.7009
    MicrosoftWindows 10 Version 21H2
    • 10.0.19044.0 – < 10.0.19044.5608
    • 10.0.19044.5608
    MicrosoftWindows 10 Version 22H2
    • 10.0.19045.0 – < 10.0.19045.5608
    • 10.0.19045.5608
    MicrosoftWindows 11 version 22H2
    • 10.0.22621.0 – < 10.0.22621.5039
    • 10.0.22621.5039
    MicrosoftWindows 11 version 22H3
    • 10.0.22631.0 – < 10.0.22631.5039
    • 10.0.22631.5039
    MicrosoftWindows 11 Version 23H2
    • 10.0.22631.0 – < 10.0.22631.5039
    • 10.0.22631.5039
    MicrosoftWindows 11 Version 24H2
    • 10.0.26100.0 – < 10.0.26100.3476
    • 10.0.26100.3476
    MicrosoftWindows Server 2012
    • 6.2.9200.0 – < 6.2.9200.25368
    • 6.2.9200.25368
    MicrosoftWindows Server 2012 (Server Core installation)
    • 6.2.9200.0 – < 6.2.9200.25368
    • 6.2.9200.25368
    MicrosoftWindows Server 2012 R2
    • 6.3.9600.0 – < 6.3.9600.22470
    • 6.3.9600.22470
    MicrosoftWindows Server 2012 R2 (Server Core installation)
    • 6.3.9600.0 – < 6.3.9600.22470
    • 6.3.9600.22470
    MicrosoftWindows Server 2016
    • 10.0.14393.0 – < 10.0.14393.7876
    • 10.0.14393.7876
    MicrosoftWindows Server 2016 (Server Core installation)
    • 10.0.14393.0 – < 10.0.14393.7876
    • 10.0.14393.7876
    MicrosoftWindows Server 2019
    • 10.0.17763.0 – < 10.0.17763.7009
    • 10.0.17763.7009
    MicrosoftWindows Server 2019 (Server Core installation)
    • 10.0.17763.0 – < 10.0.17763.7009
    • 10.0.17763.7009
    MicrosoftWindows Server 2022
    • 10.0.20348.0 – < 10.0.20348.3328
    • 10.0.20348.3328
    MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)
    • 10.0.25398.0 – < 10.0.25398.1486
    • 10.0.25398.1486
    MicrosoftWindows Server 2025
    • 10.0.26100.0 – < 10.0.26100.3476
    • 10.0.26100.3476
    MicrosoftWindows Server 2025 (Server Core installation)
    • 10.0.26100.0 – < 10.0.26100.3476
    • 10.0.26100.3476

    Vendors and products

    Affected operating systems

    Affected operating systems
    Windowsmicrosoftwindows_10_1507—
    Windowsmicrosoftwindows_10_1607—
    Windowsmicrosoftwindows_10_1809—
    Windowsmicrosoftwindows_10_21h2—
    Windowsmicrosoftwindows_10_22h2—
    Windowsmicrosoftwindows_11_22h2—
    Windowsmicrosoftwindows_11_23h2—
    Windowsmicrosoftwindows_11_24h2—
    Windowsmicrosoftwindows_server_2012r2
    Windowsmicrosoftwindows_server_2012—
    Windowsmicrosoftwindows_server_2016—
    Windowsmicrosoftwindows_server_2019—
    Windowsmicrosoftwindows_server_2022—
    Windowsmicrosoftwindows_server_2022_23h2—
    Windowsmicrosoftwindows_server_2025—

    Weakness classes (CWE)

    • CWE-532Insertion of Sensitive Information into Log File

      Base

      The product writes sensitive information to a log file.

      Entry at MITRE CWE-532

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2025-24984
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-24984"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-24984.svg?lang=en" alt="CVE-2025-24984 – NEOSEC Intel" height="20"></a>