CWE-532 Detail

CWE-532

Name

Insertion of Sensitive Information into Log File

Likelihood

Medium

Status

Incomplete

Published

2006-07-19
00h00 +00:00

Modified

2024-11-19
00h00 +00:00

Official links

CWE Mitre.org

Notifications for a CWE

Stay informed of any changes for a specific CWE.

Notifications manage

List of Notifications

Notifications for a CWE

Stay informed of any changes for a specific CWE.

Parameters

You can specify a title that will be retrieved in the alerts that will be sent out.

Specify the CWE ID you wish to monitor.

Planning

Month

Next run calculation

Day

Weekday

Hour

Minute

Creation date

Last execution

Next execution

Functionality requiring a connection

This feature, which allows you to receive alerts, is only active when you are logged into your account.

Name: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

General Informations

Modes Of Introduction

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

Common Consequences

Scope	Impact	Likelihood
Confidentiality	Read Application Data Note: Logging sensitive user data, full path names, or system information often provides attackers with an additional, less-protected path to acquiring the information.

Observed Examples

References	Description
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

Potential Mitigations

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.

Detection Methods

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.)
Effectiveness : High

Vulnerability Mapping Notes

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.
Comment : 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.

Related Attack Patterns

CAPEC-ID	Attack Pattern Name
CAPEC-215	Fuzzing for application mapping An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes the application's log or error messages returned. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to observe the application's log and error messages, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash.

Submission

Name	Organization	Date	Date release	Version
Anonymous Tool Vendor (under NDA)		2006-07-19 +00:00	2006-07-19 +00:00	Draft 3

Modifications

Name	Organization	Date	Comment
Sean Eidemiller	Cigital	2008-07-01 +00:00	added/updated demonstrative examples
Eric Dalci	Cigital	2008-07-01 +00:00	updated Potential_Mitigations, Time_of_Introduction
CWE Content Team	MITRE	2008-09-08 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2009-03-10 +00:00	updated Relationships
CWE Content Team	MITRE	2009-07-27 +00:00	updated Common_Consequences, Description, Likelihood_of_Exploit, Potential_Mitigations
CWE Content Team	MITRE	2011-03-29 +00:00	updated Name
CWE Content Team	MITRE	2011-06-01 +00:00	updated Common_Consequences, Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2012-05-11 +00:00	updated Related_Attack_Patterns, Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2014-02-18 +00:00	updated Demonstrative_Examples
CWE Content Team	MITRE	2014-07-30 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2015-12-07 +00:00	updated Relationships
CWE Content Team	MITRE	2017-11-08 +00:00	updated Modes_of_Introduction, Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2018-03-27 +00:00	updated Description, Potential_Mitigations, Relationships
CWE Content Team	MITRE	2019-01-03 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2019-06-20 +00:00	updated Name, Relationships
CWE Content Team	MITRE	2019-09-19 +00:00	updated Demonstrative_Examples, Observed_Examples
CWE Content Team	MITRE	2020-02-24 +00:00	updated Name, Relationships, Type
CWE Content Team	MITRE	2021-10-28 +00:00	updated Relationships
CWE Content Team	MITRE	2023-04-27 +00:00	updated Detection_Factors, Relationships
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2023-10-26 +00:00	updated Demonstrative_Examples, Observed_Examples
CWE Content Team	MITRE	2024-11-19 +00:00	updated Common_Consequences, Description, Diagram