Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-311 (敏感数据加密缺失) — Vulnerability Class 257

257 vulnerabilities classified as CWE-311 (敏感数据加密缺失). AI Chinese analysis included.

CWE-311 represents a critical data protection weakness where software fails to encrypt sensitive information before storage or transmission, leaving confidential data exposed in plaintext. Attackers typically exploit this vulnerability by intercepting network traffic through man-in-the-middle attacks or by gaining unauthorized physical or logical access to storage systems, allowing them to read credentials, financial records, or personal identifiable information without obstruction. To mitigate this risk, developers must implement robust cryptographic standards, such as AES-256 for data at rest and TLS 1.3 for data in transit, ensuring that all sensitive payloads are securely encoded. Furthermore, rigorous code reviews and automated static analysis tools should be employed to detect missing encryption calls, while strict key management practices guarantee that cryptographic keys themselves remain protected from compromise, thereby maintaining the confidentiality and integrity of the entire system.

MITRE CWE Description
The product does not encrypt sensitive or critical information before storage or transmission.
Common Consequences (2)
ConfidentialityRead 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…
Confidentiality, IntegrityModify 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 communica…
Mitigations (5)
RequirementsClearly 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 DesignEnsure 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…
Architecture and DesignWhen 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 1…
Architecture and DesignCompartmentalize 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 separatio…
Implementation, Architecture and DesignWhen 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.
Examples (2)
This code writes a user's login information to a cookie so the user does not have to login again later.
function persistLogin($username, $password){ $data = array("username" => $username, "password"=> $password); setcookie ("userdata", $data); }
Bad · PHP
The following code attempts to establish a connection, read in a password, then store it to a buffer.
server.sin_family = AF_INET; hp = gethostbyname(argv[1]); if (hp==NULL) error("Unknown host"); memcpy( (char *)&server.sin_addr,(char *)hp->h_addr,hp->h_length); if (argc < 3) port = 80; else port = (unsigned short)atoi(argv[3]); server.sin_port = htons(port); if (connect(sock, (struct sockaddr *)&server, sizeof server) < 0) error("Connecting"); ... while ((n=read(sock,buffer,BUFSIZE-1))!=-1) { write(dfd,password_buffer,n); ...
Bad · C
CVE IDTitleCVSSSeverityPublished
CVE-2016-10685 pk-app-wonderbox 安全漏洞 — pk-app-wonderbox node module 8.1 -2018-06-04
CVE-2016-10686 fis-sass-all 安全漏洞 — fis-sass-all node module 8.1 -2018-06-04
CVE-2016-10687 windows-selenium-chromedriver 安全漏洞 — windows-selenium-chromedriver node module 8.1 -2018-06-04
CVE-2016-10688 Haxe 3 安全漏洞 — haxe3 node module 8.1 -2018-06-04
CVE-2016-10689 windows-iedriver模块安全漏洞 — windows-iedriver node module 8.1 -2018-06-04
CVE-2016-10690 openframe-ascii-image模块安全漏洞 — openframe-ascii-image node module 8.1 -2018-06-04
CVE-2016-10691 windows-seleniumjar 安全漏洞 — windows-seleniumjar node module 8.1 -2018-06-04
CVE-2016-10693 pm2-kafka 安全漏洞 — pm2-kafka node module 8.1 -2018-06-04
CVE-2016-10694 alto-saxophone 安全漏洞 — alto-saxophone node module 8.1 -2018-06-04
CVE-2016-10574 apk-parser3 安全漏洞 — apk-parser3 node module 8.1 -2018-06-01
CVE-2016-10575 Kindlegen 安全漏洞 — kindlegen node module 8.1 -2018-06-01
CVE-2016-10576 fuseki 安全漏洞 — fuseki node module 8.1 -2018-06-01
CVE-2016-10579 chromedriver 安全漏洞 — chromedriver node module 8.1 -2018-06-01
CVE-2016-10580 nodewebkit 安全漏洞 — nodewebkit node module 8.1 -2018-06-01
CVE-2016-10581 steroids 加密问题漏洞 — steroids node module 8.1 -2018-06-01
CVE-2016-10582 closurecompiler 安全漏洞 — closurecompiler node module 8.1 -2018-06-01
CVE-2016-10585 XLware libxl 安全漏洞 — libxl node module 8.1 -2018-06-01
CVE-2016-10587 wasdk 安全漏洞 — wasdk node module 8.1 -2018-06-01
CVE-2016-10588 nw 安全漏洞 — nw node module 8.1 -2018-06-01
CVE-2016-10592 jser-stat 安全漏洞 — jser-stat node module 8.1 -2018-06-01
CVE-2016-10594 ipip 安全漏洞 — ipip node module 8.1 -2018-06-01
CVE-2016-10595 jdf-sass 安全漏洞 — jdf-sass node module 8.1 -2018-06-01
CVE-2016-10596 imageoptim 安全漏洞 — imageoptim node module 8.1 -2018-06-01
CVE-2016-10597 cobalt-cli 安全漏洞 — cobalt-cli node module 5.9 -2018-06-01
CVE-2016-10598 arrayfire-js 安全漏洞 — arrayfire-js node module 8.1 -2018-06-01
CVE-2016-10599 sauce-connect 安全漏洞 — sauce-connect node module 8.1 -2018-06-01
CVE-2016-10600 webrtc-native 安全漏洞 — webrtc-native node module 8.1 -2018-06-01
CVE-2016-10602 haxe 安全漏洞 — haxe node module 8.1 -2018-06-01
CVE-2016-10603 air-sdk 安全漏洞 — air-sdk node module 8.1 -2018-06-01
CVE-2016-10604 dalek-browser-chrome 安全漏洞 — dalek-browser-chrome node module 8.1 -2018-06-01

Vulnerabilities classified as CWE-311 (敏感数据加密缺失) represent 257 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.