CWE-256: Plaintext Storage of a Password

Code Examples & CVEs

Demonstrative Examples

The following code reads a password from a properties file and uses the password to connect to a database.

This code will run successfully, but anyone who has access to config.properties can read the value of password. If a devious employee has access to this information, they can use it to break into the system.

BadJava

...Properties prop = new Properties();prop.load(new FileInputStream("config.properties"));String password = prop.getProperty("password");DriverManager.getConnection(url, usr, password);...

The following code reads a password from the registry and uses the password to create a new network credential.

This code will run successfully, but anyone who has access to the registry key used to store the password can read the value of password. If a devious employee has access to this information, they can use it to break into the system

BadJava

...String password = regKey.GetValue(passKey).toString();NetworkCredential netCred = new NetworkCredential(username,password,domain);...

The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.

This Java example shows a properties file with a cleartext username / password pair.

BadJava

# Java Web App ResourceBundle properties file                      ...webapp.ldap.username=secretUsernamewebapp.ldap.password=secretPassword...

The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.

This Java example shows a properties file with a cleartext username / password pair.

BadASP.NET

...<connectionStrings><add name="ud_DEV" connectionString="connectDB=uDB; uid=db2admin; pwd=password; dbalias=uDB;" providerName="System.Data.Odbc" /></connectionStrings>...

Observed CVE Examples (1)

CVE-2022-30275

Remote Terminal Unit (RTU) uses a driver that relies on a password stored in plaintext.

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-256 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-256, Plaintext Storage of a Password, 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 Plaintext Storage of a Password during Architecture and Design

MITRE associates mitigation with Architecture and Design; documented detection approaches include Automated Static Analysis; recorded impacts include Gain Privileges or Assume Identity. Use these source-defined anchors to turn CWE-256 into implementation, review, and verification checks for the affected component.

CWE-256: Plaintext Storage of a Password — MITRE CWE

Triage CWE-256 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-256, Plaintext Storage of a Password, 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-256

Apply MITRE's full root-cause mapping guidance when using CWE-256, Plaintext Storage of a Password. 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-256 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-256, Plaintext Storage of a Password. 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-256: Plaintext Storage of a Password?+

CWE-256: Plaintext Storage of a Password is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product stores a password in plaintext within resources such as memory or files.

What are the security consequences of Plaintext Storage of a Password?+

If exploited, CWE-256 (Plaintext Storage of a Password) it can compromise Access Control, leading to outcomes such as Gain Privileges or Assume Identity.

How do you prevent or mitigate Plaintext Storage of a Password?+

Recommended mitigations for CWE-256 include: Avoid storing passwords in easily accessible locations. Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext. A programmer might attempt to remedy the password management problem by obscuring the password with an encoding function, such as base 64 encoding, but this effort does not adequately protect the password because the encoding can be detected and decoded easily.

Which programming languages are affected by Plaintext Storage of a Password?+

CWE-256 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 Plaintext Storage of a Password?+

MITRE documents real CVEs mapped to CWE-256, including CVE-2022-30275. 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-256 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-256: Plaintext Storage of a Password

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Phase

Description

Phase

Description

Effectiveness

Detection Methods

Code Examples & CVEs

Demonstrative Examples

Observed CVE Examples (1)

CWE Relationships

Parent Weaknesses

Source-backed guidance

Verify controls for CWE-256 with SSDF evidence

Address Plaintext Storage of a Password during Architecture and Design

Triage CWE-256 against known exploitation evidence

Apply precise root-cause mapping to CWE-256

Validate CWE-256 with root-cause mapping checks

Frequently Asked Questions

Learn More