ClassDraft

CWE-311Missing Encryption of Sensitive Data

Category: data-exposure

Description

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

Common consequences· 2

  • Confidentiality — Read Application Data
    If the application does not use a secure channel, such as SSL, to exchange sensitive information, it is possible for an attacker with access to the network traffic to sniff packets from the connection and uncover the data. This attack is not technically difficult, but does require physical access to some portion of the network over which the sensitive data travels. This access is usually somewhere near where the user is connected to the network (such as a colleague on the company network) but can be anywhere along the path from the user to the end server.
  • Confidentiality / Integrity — Modify Application Data
    Omitting the use of encryption in any program which transfers data over a network of any kind should be considered on par with delivering the data sent to each user on the local networks of both the sender and receiver. Worse, this omission allows for the injection of data into a stream of communication between two parties -- with no means for the victims to separate valid data from invalid. In this day of widespread network attacks and password collection sniffers, it is an unnecessary risk to omit encryption from the design of any system which might benefit from it.

Potential mitigations· 5

  • [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]
  • [Architecture and Design]
  • [Architecture and Design]
  • [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.

Related CAPEC attack patterns· 14

CAPEC-157CAPEC-158CAPEC-204CAPEC-31CAPEC-37CAPEC-383CAPEC-384CAPEC-385CAPEC-386CAPEC-387CAPEC-388CAPEC-477CAPEC-609CAPEC-65

References

  1. https://cwe.mitre.org/data/definitions/311.html

Exploits (incoming)14

TypeTargetConfidenceTier
AttackPatternApplication API Button Hijackingcapec-388100%live
AttackPatternNavigation Remapping To Propagate Malicious Contentcapec-387100%live
AttackPatternSniffing Network Trafficcapec-158100%live
AttackPatternTransaction or Event Tampering via Application API Manipulationcapec-385100%live
AttackPatternSignature Spoofing by Mixing Signed and Unsigned Contentcapec-477100%live
AttackPatternSniffing Attackscapec-157100%live
AttackPatternAccessing/Intercepting/Modifying HTTP Cookiescapec-31100%live
AttackPatternRetrieve Embedded Sensitive Datacapec-37100%live
AttackPatternApplication API Message Manipulation via Man-in-the-Middlecapec-384100%live
AttackPatternLifting Sensitive Data Embedded in Cachecapec-204100%live
AttackPatternSniff Application Codecapec-65100%live
AttackPatternHarvesting Information via API Event Monitoringcapec-383100%live
AttackPatternCellular Traffic Interceptcapec-609100%live
AttackPatternApplication API Navigation Remappingcapec-386100%live

Compliance frameworks addressing this (incoming)12

TypeTargetConfidenceTier
ComplianceControldora-art12100%live
ComplianceControlcra-annexi-1100%live
ComplianceControlnis2-art21h100%live
ComplianceControlgdpr-art35100%live
ComplianceControlgdpr-art25100%live
ComplianceControlowasp_top10-a04100%live
ComplianceControlgdpr-art34100%live
ComplianceControlcra-art13100%live
ComplianceControldora-art9100%live
ComplianceControlowasp_top10-a02100%live
ComplianceControlpci_dss_v4-r3100%live
ComplianceControlgdpr-art32100%live

(incoming)6

TypeTargetConfidenceTier
VulnerabilityCVE-2025-29314cve-2025-293140%live
VulnerabilityCVE-2025-48981cve-2025-489810%live
VulnerabilityCVE-2025-69969cve-2025-699690%live
VulnerabilityCVE-2026-27944cve-2026-279440%live
VulnerabilityCVE-2026-28678cve-2026-286780%live
VulnerabilityCVE-2026-32891cve-2026-328910%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Storage of Sensitive Data in a Mechanism without Access Control
CWE
Inadequate Encryption Strength
CWE
Insufficiently Protected Credentials
CWE
Exposure of Sensitive System Information to an Unauthorized Control Sphere
CWE
Omission of Security-relevant Information
CWE
Exposure of Sensitive Information to an Unauthorized Actor
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.