nday
CVE-2021-3711

SM2 Decryption Buffer Overflow

OpenSSL / OpenSSL

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

remote, unauthenticated
AV:N, PR:N, UI:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from NVD's analysts
network
AV:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from NVD's analysts
no authentication required
PR:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from NVD's analysts
no user interaction
UI:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from NVD's analysts
MySQL
CPE names NVD's analysts give as vulnerable: a:oracle:mysql_connectors, a:oracle:mysql_enterprise_monitor, a:oracle:mysql_server
PeopleSoft
CPE names NVD's analysts give as vulnerable: a:oracle:peoplesoft_enterprise_peopletools
JD Edwards
CPE names NVD's analysts give as vulnerable: a:oracle:jd_edwards_enterpriseone_tools, a:oracle:jd_edwards_world_security
OpenSSL
affected products in the CVE record: OpenSSL · OpenSSLCPE names NVD's analysts give as vulnerable: a:openssl:openssl
database
CPE names NVD's analysts give as vulnerable: a:oracle:mysql_connectors, a:oracle:mysql_enterprise_monitor, a:oracle:mysql_serverthe product type of MySQL in nday's product registry
enterprise application (ERP/CRM)
CPE names NVD's analysts give as vulnerable: a:oracle:jd_edwards_enterpriseone_tools, a:oracle:jd_edwards_world_security, a:oracle:peoplesoft_enterprise_peopletoolsthe product type of JD Edwards and PeopleSoft in nday's product registry
open-source library / framework
affected products in the CVE record: OpenSSL · OpenSSLCPE names NVD's analysts give as vulnerable: a:openssl:opensslthe product type of OpenSSL in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2021-08-24T14:50Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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).

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by openssl.

src cvelist · nday , bulk import · raw
{
  "id": 233915,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2021-3711",
  "occurred_at": "2021-08-24T14:50:13.114Z",
  "observed_at": "2026-11-13T05:37:17.325681Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "ssvc": {
      "timestamp": "2026-10-08T20:59:50.338167Z",
      "automatable": "yes",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2021-08-24T14:50:13.114Z",
    "assigner_short_name": "openssl"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.