CWE-311: Missing Encryption of Sensitive Data

ClassDraftExploit Likelihood: High

The product does not encrypt sensitive or critical information before storage or transmission.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple
Vulnerability Mapping
DISCOURAGED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-311 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-311, Missing Encryption of Sensitive Data, 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

Apply Libraries or Frameworks controls for Missing Encryption of Sensitive Data

MITRE associates mitigation with Requirements, Architecture and Design, and Implementation; the listed strategies include Libraries or Frameworks, Separation of Privilege, and Attack Surface Reduction; documented detection approaches include Manual Analysis, Automated Analysis, Manual Static Analysis - Binary or Bytecode, and Dynamic Analysis with Automated Results Interpretation. Use these source-defined anchors to turn CWE-311 into implementation, review, and verification checks for the affected component.

CWE-311: Missing Encryption of Sensitive DataMITRE CWE

Triage CWE-311 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-311, Missing Encryption of Sensitive Data, 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-311

Apply MITRE's full root-cause mapping guidance when using CWE-311, Missing Encryption of Sensitive Data. 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-311 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-311, Missing Encryption of Sensitive Data. 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-311: Missing Encryption of Sensitive Data?+

CWE-311: Missing Encryption of Sensitive Data is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not encrypt sensitive or critical information before storage or transmission.

What are the security consequences of Missing Encryption of Sensitive Data?+

If exploited, CWE-311 (Missing Encryption of Sensitive Data) it can compromise Confidentiality and Integrity, leading to outcomes such as Read Application Data and Modify Application Data.

How do you prevent or mitigate Missing Encryption of Sensitive Data?+

Recommended mitigations for CWE-311 include: Clearly specify which data or resources are valuable enough that they should be protected by encryption. Require that any transmission or storage of this data/resource should use well-vetted encryption algorithms. Ensure that encryption is properly integrated into the system design, including but not necessarily limited to: Encryption that is needed to store or transmit private data of the users of the system Encryption that is needed to protect the system itself from unauthorized disclosure or tampering Identify the separate needs and contexts for encryption: One-way (i.e., only the user or recipient needs to have the key). This can be achieved using public key cryptography, or other techniques in which the encrypting party (i.e., the product) does not need to have access to a private key. Two-way (i.e., the encryption can be automatically performed on behalf of a user, but the key must be available so that the plaintext can be automatically recoverable by that user). This requires storage of the private key in a format that is recoverable only by the user (or perhaps by the operating system) in a way that cannot be recovered by others. Using threat modeling or other techniques, assume that data can be compromised through a separate vulnerability or weakness, and determine where encryption will be most effective. Ensure that data that should be private is not being inadvertently exposed using weaknesses such as insecure permissions (CWE-732). [REF-7]

How is Missing Encryption of Sensitive Data detected?+

CWE-311 can be detected using Manual Analysis, Automated Analysis, Manual Static Analysis - Binary or Bytecode, Dynamic Analysis with Automated Results Interpretation, Dynamic Analysis with Manual Results Interpretation and Manual Static Analysis - Source Code. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Missing Encryption of Sensitive Data?+

CWE-311 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 Missing Encryption of Sensitive Data?+

MITRE documents real CVEs mapped to CWE-311, including CVE-2022-26390, CVE-2009-2272, CVE-2009-1466, CVE-2009-0152 and CVE-2009-1603. 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-311 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
CWE-311: Missing Encryption of Sensitive Data | CWE Lookup | InventiveHQ