CVE-2025-24984KEV · OVERDUECWE-532

Windows NTFS Information Disclosure Vulnerability

Medium · published March 11, 2025

Patch now

The score understates this — it's already being exploited

CVSS calls it medium at 4.6. It is confirmed in active exploitation. It sits in the 80.5th percentile for exploit probability.

571
days past CISA
deadline
CVSS v3.1
4.6
EPSS
2%
Percentile
80.5
In the wild
Confirmed
What it is

⚠️ A physical attack is all it takes! An unauthorized attacker can exploit sensitive data leaks in Windows NTFS log files — think of it as leaving your diary open on the kitchen table for anyone to read. 📖💔 Imagine you’ve left a detailed journal on the kitchen counter, revealing personal secrets. In this case, Windows NTFS is doing the same, accidentally letting unauthorized eyes catch a glimpse of sensitive information that should remain private. This vulnerability allows attackers to potentially access sensitive information stored in log files, leading to unauthorized disclosure of data. If an attacker manages to gain physical access to the machine, they could exploit this flaw to gather critical information, which could escalate to more serious security breaches. That's definitely a recipe for disaster!

Put simply

Imagine you’ve left a detailed journal on the kitchen counter, revealing personal secrets. In this case, Windows NTFS is doing the same, accidentally letting unauthorized eyes catch a glimpse of sensitive information that should remain private. The vulnerability occurs due to the insertion of sensitive information into log files without proper access controls, allowing unauthorized users to disclose secrets if they have physical access to the affected machine.

What to do

This vulnerability allows attackers to potentially access sensitive information stored in log files, leading to unauthorized disclosure of data. If an attacker manages to gain physical access to the machine, they could exploit this flaw to gather critical information, which could escalate to more serious security breaches. That's definitely a recipe for disaster! To mitigate this risk, ensure that sensitive log data is properly sanitized and stored securely. Review access controls for log files and limit physical access to machines that handle sensitive information. Additionally, consider implementing regular log audits to detect any unauthorized access or anomalies. You’ve got this! With the right steps, you can lock down those log files and keep your data secure. 🛡️✨

The record
Technical detail
CVSS v3.1
4.6 · MEDIUM
Vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:F/RL:O/RC:C
CVSS v4.0
Not supplied
EPSS
0.01994 · 80.5th percentile
Weakness
CWE-532 · Insertion of Sensitive Information into Log File
Published
2025-03-11T16:59Z
KEV added
2025-03-11 · due 2025-04-01
EPSS history
Timeline
  • 11 MAR 16:59Z
    Windows NTFS Information Disclosure Vulnerability
    cvelistv5
  • 11 MAR 00:00Z
    Added to CISA KEV — remediate by Apr 1
    kev