Unknown
CVE-2021-3712
CVE-2021-3712
Description
ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL’s own “d2i” functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the “data” and “length” fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the “data” field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).
Add Assessment
No one has assessed this topic. Be the first to add your voice to the community.
CVSS V3 Severity and Metrics
General Information
Vendors
- debian,
- mcafee,
- netapp,
- openssl,
- oracle,
- siemens,
- tenable
Products
- clustered data ontap -,
- clustered data ontap antivirus connector -,
- communications cloud native core console 1.9.0,
- communications cloud native core security edge protection proxy 1.7.0,
- communications cloud native core unified data repository 1.15.0,
- communications session border controller 8.4,
- communications session border controller 9.0,
- communications unified session manager 8.2.5,
- communications unified session manager 8.4.5,
- debian linux 10.0,
- debian linux 11.0,
- debian linux 9.0,
- e-series santricity os controller,
- enterprise communications broker 3.2.0,
- enterprise communications broker 3.3.0,
- enterprise session border controller 8.4,
- enterprise session border controller 9.0,
- epolicy orchestrator,
- epolicy orchestrator 5.10.0,
- essbase,
- essbase 21.3,
- hci management node -,
- health sciences inform publisher 6.2.1.0,
- health sciences inform publisher 6.3.1.1,
- jd edwards enterpriseone tools,
- jd edwards world security a9.4,
- manageability software development kit -,
- mysql connectors,
- mysql enterprise monitor,
- mysql server,
- mysql workbench,
- nessus network monitor,
- openssl,
- peoplesoft enterprise peopletools 8.57,
- peoplesoft enterprise peopletools 8.58,
- peoplesoft enterprise peopletools 8.59,
- santricity smi-s provider -,
- secure backup 18.1.0.1.0,
- sinec infrastructure network services,
- solidfire -,
- storage encryption -,
- tenable.sc,
- zfs storage appliance kit 8.8
References
Advisory
