CVE-2021-3711 — SM2 Decryption Buffer Overflow
In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k).
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 87.8% (30-day exploitation probability)+15
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — www.oracle.com (NIST National Vulnerability Database)
- Documented patch — www.oracle.com (NIST National Vulnerability Database)
- Documented patch — www.oracle.com (NIST National Vulnerability Database)
- Rust Openssl-src: fixed in version 111.16.0 — github.com (GitHub Security Advisories)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Netapp Active Iq Unified Manager, Netapp Clustered Data Ontap…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Debian | Debian Linux | version 11.0version 10.0 | Vulnerable | NIST National Vulnerability Database |
| Netapp | Active Iq Unified Manager | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Clustered Data Ontap | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Clustered Data Ontap Antivirus Connector | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | E-series Santricity Os Controller | ≥ 11.0 and ≤ 11.50.2 | Vulnerable | NIST National Vulnerability Database |
| Netapp | Hci Management Node | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Manageability Software Development Kit | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Oncommand Insight | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Oncommand Workflow Automation | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Santricity Smi-s Provider | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Snapcenter | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Solidfire | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Storage Encryption | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Openssl | Openssl | ≥ 1.1.1 and < 1.1.1l | Vulnerable | NIST National Vulnerability Database |
| Openssl | Openssl | version Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k) | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Oracle | Communications Cloud Native Core Security Edge Protection Proxy | version 1.7.0 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Communications Cloud Native Core Unified Data Repository | version 1.15.0 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Communications Session Border Controller | version 8.4version 9.0 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Communications Unified Session Manager | version 8.4.5version 8.2.5 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Enterprise Communications Broker | version 3.2.0version 3.3.0 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Enterprise Session Border Controller | version 9.0version 8.4 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Essbase | < 11.1.2.4.47≥ 21.1 and < 21.3 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Health Sciences Inform Publisher | version 6.3.1.1version 6.2.1.1 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Jd Edwards Enterpriseone Tools | < 9.2.6.3 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Jd Edwards World Security | version a9.4 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Mysql Connectors | ≤ 8.0.27 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Mysql Enterprise Monitor | ≤ 8.0.25 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Mysql Server | ≥ 5.7.0 and ≤ 5.7.35≥ 8.0.0 and ≤ 8.0.26 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Peoplesoft Enterprise Peopletools | version 8.58version 8.57version 8.59 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Zfs Storage Appliance Kit | version 8.8 | Vulnerable | NIST National Vulnerability Database |
| Tenable | Nessus Network Monitor | ≤ 5.13.1 | Vulnerable | NIST National Vulnerability Database |
| Tenable | Tenable.sc | ≥ 5.16.0 and ≤ 5.19.1 | Vulnerable | NIST National Vulnerability Database |
| Rust | Openssl-src | < 111.16.0 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.5 | CVSS 2.0 | High | 10.0 | 6.4 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 87.82%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Analysis and videos
CVE-2021-3711: OpenSSL SM2 Decryption Buffer Overflow
CVE-2021-3711 is a buffer overflow in the SM2 decryption code of OpenSSL. The buffer size calculated during the first EVP_PKEY_decrypt() call can be smaller than the size needed by the second call, which may let attacker-chosen data overflow the buffer by up to 62 bytes. The NVD record gives it a CVSS 3.1 score of 9.8 (critical), and the fix is in OpenSSL 1.1.1l. The CVE is not listed in CISA KEV and no confirmed exploitation appears in the sources consulted.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · rust/openssl-src
- Affected products added · openssl/openssl
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 9.8
- Source status changed · → Modified
- Record created in this database
- 2021
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
26 on the record
- www.openssl.org/news/secadv/20210824.txt
- www.oracle.com/security-alerts/cpuoct2021.html
- www.oracle.com/security-alerts/cpujan2022.html
- www.oracle.com/security-alerts/cpuapr2022.html
- security.netapp.com/advisory/ntap-20211022-0003
- lists.apache.org/thread.html/r18995de860f0e63635f3008fd2a6aca82394249476d21691e7c59c9e
- security.netapp.com/advisory/ntap-20210827-0010/
- git.openssl.org/gitweb/
- security.gentoo.org/glsa/202210-02
- security.gentoo.org/glsa/202209-02
- www.openwall.com/lists/oss-security/2021/08/26/2
- security.netapp.com/advisory/ntap-20211022-0003/
- github.com/advisories/GHSA-5ww6-px42-wc85
- lists.apache.org/thread.html/rad5d9f83f0d11fb3f8bb148d179b8a9ad7c6a17f18d70e5805a713d1
- cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- www.tenable.com/security/tns-2022-02
- security.netapp.com/advisory/ntap-20240621-0006/
- lists.apache.org/thread.html/r18995de860f0e63635f3008fd2a6aca82394249476d21691e7c59c9e
- git.openssl.org/gitweb/
- security.netapp.com/advisory/ntap-20210827-0010
- www.tenable.com/security/tns-2021-16
- lists.apache.org/thread.html/rad5d9f83f0d11fb3f8bb148d179b8a9ad7c6a17f18d70e5805a713d1
- rustsec.org/advisories/RUSTSEC-2021-0097.html
- security.netapp.com/advisory/ntap-20240621-0006
- www.debian.org/security/2021/dsa-4963
- nvd.nist.gov/vuln/detail/CVE-2021-3711
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-84782 DTLS Retransmits Handshake Messages From a Stale Buffer Offset 16d
- High CVE-2026-84784 QUIC: Unbounded RETIRE_CONNECTION_ID Backlog 16d
- High CVE-2026-84783 Use-After-Free in X.509 Extension Cache Under Concurrent Use 16d
- Medium CVE-2026-75806 Unauthenticated and Undersized DTLS 1.2 AEAD Record Causes DoS 16d
- Low CVE-2026-77696 Timing Side-Channel in SM2 Signature Generation 16d
- Medium CVE-2026-75805 NULL Pointer Dereference in CMP Client Revocation Response Handling 16d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2021-3711 is "SM2 Decryption Buffer Overflow", rated Critical. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 87.82% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.