CVE-2025-24984: CWE-532: Insertion of Sensitive Information into Log File in Microsoft Windows 10 Version 1809
Insertion of sensitive information into log file in Windows NTFS allows an unauthorized attacker to disclose information with a physical attack.
AI Analysis
Technical Summary
CVE-2025-24984 is a vulnerability identified in Microsoft Windows 10 Version 1809 (build 10.0.17763.0) involving the improper insertion of sensitive information into NTFS log files. Classified under CWE-532 (Insertion of Sensitive Information into Log File), this flaw allows an unauthorized attacker with physical access to the affected system to disclose confidential information by accessing these log files. The vulnerability arises because Windows NTFS logs, which are typically used for file system operations and auditing, inadvertently contain sensitive data that should not be recorded or exposed. The CVSS 3.1 base score is 4.6 (medium severity), with an attack vector of physical access (AV:P), low attack complexity (AC:L), no privileges required (PR:N), and no user interaction (UI:N). The impact affects confidentiality (C:H) but not integrity or availability. Exploitation requires physical access, which limits remote or network-based attacks, and no known exploits have been reported in the wild. The vulnerability was published on March 11, 2025, and no official patches have been released yet. This issue is significant for environments where physical security is not guaranteed or where sensitive data exposure through logs could lead to further compromise or data leakage. Organizations running Windows 10 Version 1809 should be aware of this risk and consider mitigation strategies including physical security enhancements and system upgrades.
Potential Impact
For European organizations, the primary impact of CVE-2025-24984 is the potential unauthorized disclosure of sensitive information through NTFS log files on Windows 10 Version 1809 systems. This can lead to confidentiality breaches, especially in sectors handling sensitive personal data, intellectual property, or critical infrastructure information. Since exploitation requires physical access, environments with less stringent physical security controls, such as shared offices, public access areas, or remote workstations, are at higher risk. The vulnerability does not affect system integrity or availability, so operational disruption is unlikely. However, data leakage could facilitate further attacks or regulatory non-compliance under GDPR, leading to reputational damage and financial penalties. Organizations relying heavily on Windows 10 Version 1809, particularly those slow to update or with legacy systems, face increased exposure. The absence of a patch means temporary mitigations must be prioritized until an official fix is available.
Mitigation Recommendations
1. Enhance physical security controls to restrict unauthorized physical access to devices running Windows 10 Version 1809, including secure office environments, locked server rooms, and controlled access to endpoints. 2. Audit and monitor NTFS log files regularly to detect any unusual or sensitive data entries and implement log management policies that minimize sensitive data logging. 3. Where feasible, upgrade affected systems to later Windows 10 versions or Windows 11, which are not reported to have this vulnerability, to eliminate exposure. 4. Employ disk encryption solutions such as BitLocker to protect data at rest, reducing the risk of data extraction from physical access. 5. Implement endpoint detection and response (EDR) tools that can alert on unauthorized physical access attempts or suspicious file access patterns. 6. Educate staff about the risks of physical access attacks and enforce strict device handling policies. 7. Maintain an inventory of systems running the vulnerable version to prioritize remediation efforts. 8. Monitor official Microsoft advisories for patches or updates addressing this vulnerability and apply them promptly once available.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Belgium, Sweden, Finland
CVE-2025-24984: CWE-532: Insertion of Sensitive Information into Log File in Microsoft Windows 10 Version 1809
Description
Insertion of sensitive information into log file in Windows NTFS allows an unauthorized attacker to disclose information with a physical attack.
AI-Powered Analysis
Technical Analysis
CVE-2025-24984 is a vulnerability identified in Microsoft Windows 10 Version 1809 (build 10.0.17763.0) involving the improper insertion of sensitive information into NTFS log files. Classified under CWE-532 (Insertion of Sensitive Information into Log File), this flaw allows an unauthorized attacker with physical access to the affected system to disclose confidential information by accessing these log files. The vulnerability arises because Windows NTFS logs, which are typically used for file system operations and auditing, inadvertently contain sensitive data that should not be recorded or exposed. The CVSS 3.1 base score is 4.6 (medium severity), with an attack vector of physical access (AV:P), low attack complexity (AC:L), no privileges required (PR:N), and no user interaction (UI:N). The impact affects confidentiality (C:H) but not integrity or availability. Exploitation requires physical access, which limits remote or network-based attacks, and no known exploits have been reported in the wild. The vulnerability was published on March 11, 2025, and no official patches have been released yet. This issue is significant for environments where physical security is not guaranteed or where sensitive data exposure through logs could lead to further compromise or data leakage. Organizations running Windows 10 Version 1809 should be aware of this risk and consider mitigation strategies including physical security enhancements and system upgrades.
Potential Impact
For European organizations, the primary impact of CVE-2025-24984 is the potential unauthorized disclosure of sensitive information through NTFS log files on Windows 10 Version 1809 systems. This can lead to confidentiality breaches, especially in sectors handling sensitive personal data, intellectual property, or critical infrastructure information. Since exploitation requires physical access, environments with less stringent physical security controls, such as shared offices, public access areas, or remote workstations, are at higher risk. The vulnerability does not affect system integrity or availability, so operational disruption is unlikely. However, data leakage could facilitate further attacks or regulatory non-compliance under GDPR, leading to reputational damage and financial penalties. Organizations relying heavily on Windows 10 Version 1809, particularly those slow to update or with legacy systems, face increased exposure. The absence of a patch means temporary mitigations must be prioritized until an official fix is available.
Mitigation Recommendations
1. Enhance physical security controls to restrict unauthorized physical access to devices running Windows 10 Version 1809, including secure office environments, locked server rooms, and controlled access to endpoints. 2. Audit and monitor NTFS log files regularly to detect any unusual or sensitive data entries and implement log management policies that minimize sensitive data logging. 3. Where feasible, upgrade affected systems to later Windows 10 versions or Windows 11, which are not reported to have this vulnerability, to eliminate exposure. 4. Employ disk encryption solutions such as BitLocker to protect data at rest, reducing the risk of data extraction from physical access. 5. Implement endpoint detection and response (EDR) tools that can alert on unauthorized physical access attempts or suspicious file access patterns. 6. Educate staff about the risks of physical access attacks and enforce strict device handling policies. 7. Maintain an inventory of systems running the vulnerable version to prioritize remediation efforts. 8. Monitor official Microsoft advisories for patches or updates addressing this vulnerability and apply them promptly once available.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- microsoft
- Date Reserved
- 2025-01-30T15:14:20.992Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682cd0f81484d88663aeb35f
Added to database: 5/20/2025, 6:59:04 PM
Last enriched: 12/17/2025, 11:57:25 PM
Last updated: 1/19/2026, 10:14:17 AM
Views: 55
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-1148: Cross-Site Request Forgery in SourceCodester Patients Waiting Area Queue Management System
MediumCVE-2026-1147: Cross Site Scripting in SourceCodester Patients Waiting Area Queue Management System
Medium19th January – Threat Intelligence Report
MediumCVE-2026-1146: Cross Site Scripting in SourceCodester Patients Waiting Area Queue Management System
MediumCVE-2025-59355: CWE-532 Insertion of Sensitive Information into Log File in Apache Software Foundation Apache Linkis
UnknownActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.