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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

270 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)
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…
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 communica…
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 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…
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 1…
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 separatio…
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.
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 ID Title CVSS Severity Published
CVE-2016-10623 macaca-chromedriver-zxa 安全漏洞 — macaca-chromedriver-zxa node module 8.1 - 2018-06-01
CVE-2016-10624 selenium-chromedriver 安全漏洞 — selenium-chromedriver node module 8.1 - 2018-06-01
CVE-2016-10625 headless-browser-lite 安全漏洞 — headless-browser-lite node module 8.1 - 2018-06-01
CVE-2016-10626 mystem3 安全漏洞 — mystem3 node module 8.1 - 2018-06-01
CVE-2016-10628 selenium-wrapper 安全漏洞 — selenium-wrapper node module 8.1 - 2018-06-01
CVE-2016-10629 nw-with-arm 安全漏洞 — nw-with-arm node module 8.1 - 2018-06-01
CVE-2016-10630 install-g-tes 安全漏洞 — install-g-test node module 5.9 - 2018-06-01
CVE-2016-10631 jvminstall安全漏洞 — jvminstall node module 8.1 - 2018-06-01
CVE-2016-10632 apk-parser2 安全漏洞 — apk-parser2 node module 8.1 - 2018-06-01
CVE-2016-10633 dwebp-bin 安全漏洞 — dwebp-bin node module 8.1 - 2018-06-01
CVE-2016-10634 scala-standalone-bin 安全漏洞 — scalajs-standalone-bin node module 8.1 - 2018-06-01
CVE-2016-10552 igniteui 安全漏洞 — igniteui node module 7.4 - 2018-05-31
CVE-2016-10557 appium-chromedriver 安全漏洞 — appium-chromedriver node module 8.1 - 2018-05-31
CVE-2016-10560 galenframework-cli 安全漏洞 — galenframework-cli node module 8.1 - 2018-05-31
CVE-2016-10562 iedriver 安全漏洞 — iedriver node module 8.1 - 2018-05-31
CVE-2016-10563 go-ipfs-deps模块安全漏洞 — go-ipfs-dep node module 7.4 - 2018-05-31
CVE-2016-10564 apk-parser 安全漏洞 — apk-parser node module 8.1 - 2018-05-31
CVE-2016-10565 operadriver 安全漏洞 — operadriver node module 8.1 - 2018-05-31
CVE-2016-10569 embedza 安全漏洞 — embedza node module 8.1 - 2018-05-31
CVE-2016-10571 bkjs-wand 安全漏洞 — bkjs-wand node module 8.1 - 2018-05-31
CVE-2016-10572 mongodb-instance 安全漏洞 — mongodb-instance node module 8.1 - 2018-05-31
CVE-2016-10558 aerospike 安全漏洞 — aerospike node module 8.1 - 2018-05-29
CVE-2016-10559 selenium-download 安全漏洞 — selenium-download node module 8.1 - 2018-05-29
CVE-2016-10566 install-nw 安全漏洞 — install-nw node module 8.1 - 2018-05-29
CVE-2016-10567 install-nw 安全漏洞 — product-monitor node module 8.1 - 2018-05-29
CVE-2016-10568 geoip-lite-country 安全漏洞 — geoip-lite-country node module 8.1 - 2018-05-29
CVE-2016-10570 pngcrush-installer 安全漏洞 — pngcrush-installer node module 8.1 - 2018-05-29
CVE-2016-10573 baryton-saxophone 安全漏洞 — baryton-saxophone node module 8.1 - 2018-05-29
CVE-2016-10577 ibm_db 安全漏洞 — ibm_db node module 8.1 - 2018-05-29
CVE-2016-10578 unicode 安全漏洞 — unicode node module 8.1 - 2018-05-29

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