CWE-311: Missing Encryption of Sensitive Data
468 CVEs have CWE-311 as their primary weakness. 1 of them are in the CISA KEV catalog. The highest EPSS score among them is 98.503%.
The product does not encrypt sensitive or critical information before storage or transmission.
Child of CWE-693: Protection Mechanism Failure
Mitigations
- 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: 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…
- Architecture and Design: 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…
- Architecture and Design: 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: 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.
Observed examples
- CVE-2022-26390: wireless battery product stores credentials and Personal Health Information (PHI) without encryption
- CVE-2009-2272: password and username stored in cleartext in a cookie
- CVE-2009-1466: password stored in cleartext in a file with insecure permissions
- CVE-2009-0152: chat program disables SSL in some circumstances even when the user says to use SSL.
- CVE-2009-1603: Chain: product uses an incorrect public exponent when generating an RSA key, which effectively disables the encryption
- CVE-2009-0964: storage of unencrypted passwords in a database
- CVE-2008-6157: storage of unencrypted passwords in a database
- CVE-2008-6828: product stores a password in cleartext in memory
- CVE-2008-1567: storage of a secret key in cleartext in a temporary file
- CVE-2008-0174: SCADA product uses HTTP Basic Authentication, which is not encrypted
- CVE-2007-5778: login credentials stored unencrypted in a registry key
- CVE-2002-1949: Passwords transmitted in cleartext.
- CVE-2008-4122: Chain: Use of HTTPS cookie without secure flag causes it to be transmitted across unencrypted HTTP.
- CVE-2008-3289: Product sends password hash in cleartext in violation of intended policy.
- CVE-2008-4390: Remote management feature sends sensitive information including passwords in cleartext.
- CVE-2007-5626: Backup routine sends password in cleartext in email.
- CVE-2004-1852: Product transmits Blowfish encryption key in cleartext.
- CVE-2008-0374: Printer sends configuration information, including administrative password, in cleartext.
- CVE-2007-4961: Chain: cleartext transmission of the MD5 hash of password (CWE-319) enables attacks against a server that is susceptible to replay (CWE-294).
- CVE-2007-4786: Product sends passwords in cleartext to a log server.
- CVE-2005-3140: Product sends file with cleartext passwords in e-mail message intended for diagnostic purposes.
Top released CVEs
KEV first, then the highest EPSS score, the highest CVSS score and the newest.
| CVE | Published | Severity | CVSS | EPSS | Description |
|---|---|---|---|---|---|
| CVE-2026-34486 | 2026-04-09 | HIGH | 7.5 | 98.503% | Missing Encryption of Sensitive Data vulnerability in Apache Tomcat due to the fix for CVE-2026-29146 allowing the bypass of the EncryptInterceptor. This issue… |
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-311'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-311'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).