CWE-532: Insertion of Sensitive Information into Log File
The product writes sensitive information to a log file.
How it's found
Insertion of Sensitive Information into Log File is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
Consequences
- Read Application Data: Logging sensitive user data, full path names, or system information often provides attackers with an additional, less-protected path to acquiring the information.
Mitigations
- Architecture and Design/Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
- Distribution: Remove debug log files before deploying the application into production.
- Operation: Protect log files against unauthorized read/write.
- Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.
How TurboPentest tests for this (white-box)
This weakness (Insertion of Sensitive Information into Log File) is caught by white-box static analysis when you connect a GitHub repo: IntegSec's Opengrep SAST rule pack carries 10 rules for it, flagging the issue directly in your source code as part of the pentest.
Frequently asked questions
What is CWE-532?
The product writes sensitive information to a log file.
How do you find Insertion of Sensitive Information into Log File?
Insertion of Sensitive Information into Log File is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
What is the impact of CWE-532?
Read Application Data: Logging sensitive user data, full path names, or system information often provides attackers with an additional, less-protected path to acquiring the information.
Does TurboPentest test for Insertion of Sensitive Information into Log File?
This weakness (Insertion of Sensitive Information into Log File) is caught by white-box static analysis when you connect a GitHub repo: IntegSec's Opengrep SAST rule pack carries 10 rules for it, flagging the issue directly in your source code as part of the pentest.
Related CWEs
Written and reviewed by
Michel Chamberland - Founder & CEO, IntegSec
CISSP, OSCP, OSCE, CEH, GIAC, CCSK · 20+ years in offensive security
Michel has spent 20+ years on offensive security teams including IBM X-Force Red and Trustwave SpiderLabs, leading penetration tests, red team engagements, and breach response for Fortune 500 customers. He is the founder of IntegSec and the architect of TurboPentest.
Find these issues before an attacker does
TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.
Start a pentest