CWE-532: Insertion of Sensitive Information into Log File

Code Examples & CVEs

Demonstrative Examples

In the following code snippet, a user's full name and credit card number are written to a log file.

BadJava

logger.info("Username: " + usernme + ", CCN: " + ccn);

This code stores location information about the current user:

When the application encounters an exception it will write the user object to the log. Because the user object contains location information, the user's location is also written to the log.

BadJava

locationClient = new LocationClient(this, this, this);locationClient.connect();currentUser.setLocation(locationClient.getLastLocation());                      ...                                            catch (Exception e) {AlertDialog.Builder builder = new AlertDialog.Builder(this);builder.setMessage("Sorry, this application has experienced an error.");AlertDialog alert = builder.create();alert.show();Log.e("ExampleActivity", "Caught exception: " + e + " While on User:" + User.toString());}

In the example below, the method getUserBankAccount retrieves a bank account object from a database using the supplied username and account number to query the database. If an SQLException is raised when querying the database, an error message is created and output to a log file.

The error message that is created includes information about the database query that may contain sensitive information about the database or query logic. In this case, the error message will expose the table name and column names used in the database. This data could be used to simplify other attacks, such as SQL injection (CWE-89) to directly access the database.

BadJava

public BankAccount getUserBankAccount(String username, String accountNumber) {                         BankAccount userAccount = null;String query = null;try {if (isAuthorizedUser(username)) {query = "SELECT * FROM accounts WHERE owner = "+ username + " AND accountID = " + accountNumber;DatabaseManager dbManager = new DatabaseManager();Connection conn = dbManager.getConnection();Statement stmt = conn.createStatement();ResultSet queryResult = stmt.executeQuery(query);userAccount = (BankAccount)queryResult.getObject(accountNumber);}} catch (SQLException ex) {String logMessage = "Unable to retrieve account information from database,\nquery: " + query;Logger.getLogger(BankManager.class.getName()).log(Level.SEVERE, logMessage, ex);}return userAccount;                      }

Observed CVE Examples (2)

CVE-2017-9615

verbose logging stores admin credentials in a world-readable log file

View Details

CVE-2018-1999036

SSH password for private key stored in build log

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-532 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-532, Insertion of Sensitive Information into Log File, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Insertion of Sensitive Information into Log File during Architecture and Design

MITRE associates mitigation with Architecture and Design, Implementation, Distribution, and Operation; documented detection approaches include Automated Static Analysis; recorded impacts include Read Application Data. Use these source-defined anchors to turn CWE-532 into implementation, review, and verification checks for the affected component.

CWE-532: Insertion of Sensitive Information into Log File — MITRE CWE

Triage CWE-532 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-532, Insertion of Sensitive Information into Log File, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-532

Apply MITRE's full root-cause mapping guidance when using CWE-532, Insertion of Sensitive Information into Log File. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-532 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-532, Insertion of Sensitive Information into Log File. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-532: Insertion of Sensitive Information into Log File?+

CWE-532: Insertion of Sensitive Information into Log File is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product writes sensitive information to a log file.

What are the security consequences of Insertion of Sensitive Information into Log File?+

If exploited, CWE-532 (Insertion of Sensitive Information into Log File) it can compromise Confidentiality, leading to outcomes such as Read Application Data.

How do you prevent or mitigate Insertion of Sensitive Information into Log File?+

Recommended mitigations for CWE-532 include: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files. Remove debug log files before deploying the application into production. Protect log files against unauthorized read/write.

Which programming languages are affected by Insertion of Sensitive Information into Log File?+

CWE-532 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Insertion of Sensitive Information into Log File?+

MITRE documents real CVEs mapped to CWE-532, including CVE-2017-9615 and CVE-2018-1999036. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-532 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-532: Insertion of Sensitive Information into Log File

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Phase

Description

Phase

Description

Phase

Description

Detection Methods

Code Examples & CVEs

Demonstrative Examples

Observed CVE Examples (2)

CWE Relationships

Parent Weaknesses

Source-backed guidance

Verify controls for CWE-532 with SSDF evidence

Address Insertion of Sensitive Information into Log File during Architecture and Design

Triage CWE-532 against known exploitation evidence

Apply precise root-cause mapping to CWE-532

Validate CWE-532 with root-cause mapping checks

Frequently Asked Questions

Learn More