Insertion of Sensitive Information into Log File

Opis

The product writes sensitive information to a log file.

Skutki

• Confidentiality

  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.

Zapobieganie

• 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.

Przykłady podatności

• CVE-2017-9615 verbose logging stores admin credentials in a world-readable log file
• CVE-2018-1999036 SSH password for private key stored in build log

Słabość nadrzędna

• CWE-538 Insertion of Sensitive Information into Externally-Accessible File or Directory
• CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

Kiedy powstaje

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

Dotyczy

Not Language-Specific