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-10646 resourcehacker 安全漏洞 — resourcehacker node module 8.1 -2018-06-04
CVE-2016-10647 node-air-sdk 安全漏洞 — node-air-sdk node module 8.1 -2018-06-04
CVE-2016-10648 marionette-socket-host 安全漏洞 — marionette-socket-host node module 8.1 -2018-06-04
CVE-2016-10649 frames-compiler 安全漏洞 — frames-compiler node module 8.1 -2018-06-04
CVE-2016-10651 webdriver-launcher 安全漏洞 — webdriver-launcher node module 8.1 -2018-06-04
CVE-2016-10652 prebuild-lwip 安全漏洞 — prebuild-lwip node module 8.1 -2018-06-04
CVE-2016-10653 xd-testing 安全漏洞 — xd-testing node module 8.1 -2018-06-04
CVE-2016-10654 sfml 安全漏洞 — sfml node module 7.4 -2018-06-04
CVE-2016-10655 clang-extra 安全漏洞 — clang-extra node module 8.1 -2018-06-04
CVE-2016-10656 qbs 安全漏洞 — qbs node module 8.1 -2018-06-04
CVE-2016-10657 co-cli-installer 安全漏洞 — co-cli-installer node module 8.1 -2018-06-04
CVE-2016-10660 fis-parser-sass-bin 安全漏洞 — fis-parser-sass-bin node module 8.1 -2018-06-04
CVE-2016-10661 phantomjs-cheniu 安全漏洞 — phantomjs-cheniu node module 8.1 -2018-06-04
CVE-2016-10662 tomita 安全漏洞 — tomita node module 8.1 -2018-06-04
CVE-2016-10663 wixtoolset 安全漏洞 — wixtoolset node module 8.1 -2018-06-04
CVE-2016-10664 msystem 安全漏洞 — mystem node module 8.1 -2018-06-04
CVE-2016-10665 herbivore 安全漏洞 — herbivore node module 8.1 -2018-06-04
CVE-2016-10667 selenium-portal 安全漏洞 — selenium-portal node module 8.1 -2018-06-04
CVE-2016-10668 libsbml 安全漏洞 — libsbml node module 8.1 -2018-06-04
CVE-2016-10669 soci 安全漏洞 — soci node module 8.1 -2018-06-04
CVE-2016-10670 windows-seleniumjar-mirror 安全漏洞 — windows-seleniumjar-mirror node module 8.1 -2018-06-04
CVE-2016-10671 mystem-wrapper 安全漏洞 — mystem-wrapper node module 8.1 -2018-06-04
CVE-2016-10672 cloudpub-redis 安全漏洞 — cloudpub-redis node module 8.1 -2018-06-04
CVE-2016-10673 ipip-coffee 安全漏洞 — ipip-coffee node module 8.1 -2018-06-04
CVE-2016-10675 libsbmlsim 安全漏洞 — libsbmlsim node module 8.1 -2018-06-04
CVE-2016-10676 rs-brightcove 安全漏洞 — rs-brightcove node module 8.1 -2018-06-04
CVE-2016-10677 google-closure-tools-latest 安全漏洞 — google-closure-tools-latest node module 8.1 -2018-06-04
CVE-2016-10678 serc.js 安全漏洞 — serc.js node module 8.1 -2018-06-04
CVE-2016-10683 arcanist 安全漏洞 — arcanist node module 8.1 -2018-06-04
CVE-2016-10684 healthcenter 安全漏洞 — healthcenter node module 8.1 -2018-06-04

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