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).
| Vulnerable Product | Search on Vulmon | Subscribe to Product |
|---|---|---|
openssl openssl |
||
debian debian linux 9.0 |
||
debian debian linux 10.0 |
||
debian debian linux 11.0 |
||
netapp santricity smi-s provider - |
||
netapp clustered data ontap - |
||
netapp clustered data ontap antivirus connector - |
||
netapp solidfire - |
||
netapp hci management node - |
||
netapp manageability software development kit - |
||
netapp storage encryption - |
||
netapp e-series santricity os controller |
||
mcafee epolicy orchestrator 5.10.0 |
||
mcafee epolicy orchestrator |
||
tenable tenable.sc |
||
tenable nessus network monitor |
||
oracle peoplesoft enterprise peopletools 8.57 |
||
oracle peoplesoft enterprise peopletools 8.58 |
||
oracle zfs storage appliance kit 8.8 |
||
oracle peoplesoft enterprise peopletools 8.59 |
||
oracle mysql server |
||
oracle mysql workbench |
||
oracle mysql enterprise monitor |
||
oracle essbase |
||
oracle secure backup 18.1.0.1.0 |
||
oracle essbase 21.3 |
||
oracle mysql connectors |
||
siemens sinec infrastructure network services |
||
oracle jd edwards world security a9.4 |
||
oracle enterprise session border controller 8.4 |
||
oracle enterprise communications broker 3.2.0 |
||
oracle communications session border controller 8.4 |
||
oracle enterprise session border controller 9.0 |
||
oracle communications session border controller 9.0 |
||
oracle communications cloud native core security edge protection proxy 1.7.0 |
||
oracle enterprise communications broker 3.3.0 |
||
oracle communications unified session manager 8.2.5 |
||
oracle communications cloud native core console 1.9.0 |
||
oracle communications cloud native core unified data repository 1.15.0 |
||
oracle health sciences inform publisher 6.3.1.1 |
||
oracle jd edwards enterpriseone tools |
||
oracle communications unified session manager 8.4.5 |
||
oracle health sciences inform publisher 6.2.1.0 |
Customers of Taiwan-based QNAP Systems are in a bit of limbo, waiting until the company releases a patch for an OpenSSL bug that the company has warned affects most of its network-attached storage (NAS) devices. The vulnerability can trigger an infinite loop that creates a denial-of-service (DoS) scenario.
Though the bug – tracked as CVE-2022-0778 and rated 7.5 (high severity) on the CVSS severity-rating scale – has been patched by OpenSSL, QNAP hasn’t gotten around to applying a fix...
On Monday, QNAP put out two security advisories about OpenSSL remote-code execution and denial-of-service (DoS) bugs, fixed last week, that affect its network-attached storage (NAS) devices.
The vulnerabilities are tracked as CVE-2021-3711 – a high-severity buffer overflow related to SM2 decryption– and CVE-2021-3712, a medium-severity flaw that can be exploited for DoS attacks and possibly for the disclosure of private memory contents.
These OpenSSL flaws are spreading ripples f...
Network-attached storage (NAS) maker QNAP is investigating and working on security updates to address remote code execution (RCE) and denial-of-service (DoS) vulnerabilities patched by OpenSSL last week.
The security flaws tracked as
and
, impact QNAP NAS device running QTS, QuTS hero, QuTScloud, and HBS 3 Hybrid Backup Sync (a backup and disaster recovery app), according to advisories [
,
] published earlier today.
The
in the SM2 cryptographic alg...
Vulmon