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

What CVEs are caused by CWE-311?

289 recorded CVEs are attributed to CWE-311, including CVE-2023-6339, CVE-2025-36751, CVE-2024-29151.

Is CWE-311 part of the OWASP Top 10?

CWE-311 maps to OWASP Top Ten 2007: Insecure Cryptographic Storage (A8) in the OWASP security taxonomy.

How is CWE-311 detected?

Manual Analysis: The characterizaton of sensitive data often requires domain-specific understanding, so manual methods are useful. However, manual efforts might not achieve desired code coverage within limited time constraints. Black box methods may produce artifacts (e.g. stored data or unencrypted network transfer) that require manual evaluation.

What are the consequences of CWE-311?

Exploiting CWE-311 can lead to: Read Application Data, Modify Application Data.

Is CWE-311 actively exploited?

289 recorded CVEs are caused by CWE-311; none are currently in CISA's KEV catalog of actively exploited flaws.

CWE-311: Missing Encryption of Sensitive Data

289 recorded CVEs are caused by CWE-311 (Missing Encryption of Sensitive Data). The highest-severity and most recent are shown first. 5 new CWE-311 CVEs have been recorded so far in 2026 (38 in 2025).

How to prevent it

Practical mitigations for CWE-311, grouped by where in the lifecycle they apply.

Requirements

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.

Architecture and Design

Ensure that encryption is properly integrated into the system design, including but not necessarily limited to:

Identify the separate needs and contexts for encryption:

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]

[object Object]
[object Object]

Architecture and Design

Libraries or Frameworks

When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations. As with all cryptographic mechanisms, the source code should be available for analysis.

For example, US government systems require FIPS 140-2 certification.

Do not develop custom or private cryptographic algorithms. They will likely be exposed to attacks that are well-understood by cryptographers. Reverse engineering techniques are mature. If the algorithm can be compromised if attackers find out how it works, then it is especially weak.

Periodically ensure that the cryptography has not become obsolete. Some older algorithms, once thought to require a billion years of computing time, can now be broken in days or hours. This includes MD4, MD5, SHA1, DES, and other algorithms that were once regarded as strong. [REF-267]

Architecture and Design

Separation of Privilege

Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.

Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

Implementation

Architecture and Design

When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for preventing common attacks.

Implementation

Attack Surface Reduction

Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.

Effectiveness: Defense in Depth — This makes it easier to spot places in the code where data is being used that is unencrypted.

CWE-311: Missing Encryption of Sensitive Data

Overview

Real-world CVEs

Common consequences

How it happens

When it is introduced

How to prevent it

How to detect it

Manual Analysis

Automated Analysis

Manual Static Analysis - Binary or Bytecode

Dynamic Analysis with Automated Results Interpretation

Dynamic Analysis with Manual Results Interpretation

Manual Static Analysis - Source Code

Automated Static Analysis - Source Code

Architecture or Design Review

Code examples

Illustrative examples

Terminology & mappings

Mapped taxonomies

Attack patterns

Frequently asked questions

What is CWE-311?

What CVEs are caused by CWE-311?

Is CWE-311 part of the OWASP Top 10?

How do you prevent CWE-311?

How is CWE-311 detected?

What are the consequences of CWE-311?

Is CWE-311 actively exploited?

References

Stay ahead of CWE-311

Overview

Real-world CVEs

Common consequences

How it happens

When it is introduced

How to prevent it

How to detect it

Manual Analysis

Automated Analysis

Manual Static Analysis - Binary or Bytecode

Dynamic Analysis with Automated Results Interpretation

Dynamic Analysis with Manual Results Interpretation

Manual Static Analysis - Source Code

Automated Static Analysis - Source Code

Architecture or Design Review

Code examples

Illustrative examples

Related weaknesses

Parent

Child

Peer

Terminology & mappings

Mapped taxonomies

Attack patterns

Frequently asked questions

What is CWE-311?

What CVEs are caused by CWE-311?

Is CWE-311 part of the OWASP Top 10?

How do you prevent CWE-311?

How is CWE-311 detected?

What are the consequences of CWE-311?

Is CWE-311 actively exploited?

References

Stay ahead of CWE-311