High severityPythonSensitive Data ExposureMEDIUM confidence
Logging Secret
A secret or credential is written to logs (CWE-532).
Standards mapping
- OWASP ASVS
- V7.1.1 (L2)V7.1.2 (L2)
Vulnerable vs. safe
Flagged by this check
logger.info("Authenticating with api_key=%s", api_key)Passes - the safe pattern
logger.info("Authenticating user %s", username)Why it matters & how to fix it
A secret or credential is written to logs (CWE-532). Logs are aggregated, retained, and widely readable, so secrets leak. Never log credentials; redact or omit the value, or log a non-reversible identifier instead.
References
Rule ID integsec-python-logging-secret - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - Sensitive Data ExposureError Stack In Response
- JavaScript / TypeScript - Sensitive Data ExposurePII PHI In Logs
- JavaScript / TypeScript - Sensitive Data ExposureSecret In Logs
- JavaScript / TypeScript - Sensitive Data ExposureSensitive Data Client Storage
- JavaScript / TypeScript - Sensitive Data ExposureSensitive Data In URL Query
- Python - Sensitive Data ExposureFlask Traceback In Response