Insertion of sensitive information into log file in Windows NTFS allows an unauthorized attacker to disclose information with a physical attack.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Windows_10_1507 | Microsoft | * | 10.0.10240.20947 (excluding) |
Windows_10_1607 | Microsoft | * | 10.0.14393.7876 (excluding) |
Windows_10_1809 | Microsoft | * | 10.0.17763.7009 (excluding) |
Windows_10_21h2 | Microsoft | * | 10.0.19044.5608 (excluding) |
Windows_10_22h2 | Microsoft | * | 10.0.19045.5608 (excluding) |
Windows_11_22h2 | Microsoft | * | 10.0.22621.5039 (excluding) |
Windows_11_23h2 | Microsoft | * | 10.0.22631.5039 (excluding) |
Windows_11_24h2 | Microsoft | * | 10.0.26100.3476 (excluding) |
Windows_server_2012 | Microsoft | - (including) | - (including) |
Windows_server_2012 | Microsoft | r2 (including) | r2 (including) |
Windows_server_2016 | Microsoft | * | 10.0.14393.7876 (excluding) |
Windows_server_2019 | Microsoft | * | 10.0.17763.7009 (excluding) |
Windows_server_2022 | Microsoft | * | 10.0.20348.3328 (excluding) |
Windows_server_2022_23h2 | Microsoft | * | 10.0.25398.1486 (excluding) |
Windows_server_2025 | Microsoft | * | 10.0.26100.3476 (excluding) |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: