CWE-312: Cleartext Storage of Sensitive Information

BaseDraft

The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-312 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-312, Cleartext Storage of Sensitive Information, 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 FrameworkNational Institute of Standards and Technology

Address Cleartext Storage of Sensitive Information during Implementation

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

CWE-312: Cleartext Storage of Sensitive InformationMITRE CWE

Triage CWE-312 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-312, Cleartext Storage of Sensitive Information, 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 CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-312

Apply MITRE's full root-cause mapping guidance when using CWE-312, Cleartext Storage of Sensitive Information. 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 GuidanceMITRE CWE

Validate CWE-312 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-312, Cleartext Storage of Sensitive Information. 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 TipsMITRE CWE

Frequently Asked Questions

What is CWE-312: Cleartext Storage of Sensitive Information?+

CWE-312: Cleartext Storage of Sensitive Information is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.

What are the security consequences of Cleartext Storage of Sensitive Information?+

If exploited, CWE-312 (Cleartext Storage of Sensitive Information) it can compromise Confidentiality, leading to outcomes such as Read Application Data.

How do you prevent or mitigate Cleartext Storage of Sensitive Information?+

Recommended mitigations for CWE-312 include: When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest. [REF-1297] [REF-1299] [REF-1301] In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.

Which programming languages are affected by Cleartext Storage of Sensitive Information?+

CWE-312 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 Cleartext Storage of Sensitive Information?+

MITRE documents real CVEs mapped to CWE-312, including CVE-2022-26390, CVE-2022-30275, CVE-2009-2272, CVE-2009-1466 and CVE-2009-0152. 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-312 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.

Learn More

Advertisement