Détail du CWE-532

The product writes sensitive information to a log file.

Modes d'introduction

Architecture and Design : COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.
Implementation
Operation

Conséquences courantes

Exemples observés

Mesures d’atténuation potentielles

Phases : Architecture and Design // Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Phases : Distribution
Remove debug log files before deploying the application into production.
Phases : Operation
Protect log files against unauthorized read/write.
Phases : Implementation
Adjust configurations appropriately when software is transitioned from a debug state to production.

Méthodes de détection

Automated Static Analysis

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Efficacité : High

Notes de cartographie des vulnérabilités

Justification : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Commentaire : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

Modèles d'attaque associés

Soumission

Modifications