Vulnetix
Try Vulnetix Request Demo
SSA-244969 PUBLISHED CVSS 7.400000095367432 HIGH

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

Risk Scores

CVSS v3.1
7.400000095367432
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H

Affected Products

VendorProductVersions
SiemensSIPLUS S7-1200 CPU 1212C DC/DC/DC (6AG1212-1AE40-2XB0)
SiemensSCALANCE W774-1 RJ45 (USA) (6GK5774-1FX00-0AB6)
SiemensSIPLUS S7-1200 CPU 1215 DC/DC/RLY (6AG1215-1HG40-4XB0)
SiemensSCALANCE W788-2 RJ45 (6GK5788-2FC00-0AB0)
SiemensSIMATIC S7-1200 CPU 1212C AC/DC/Rly (6ES7212-1BE40-0XB0)
SiemensSCALANCE X308-2 (6GK5308-2FL00-2AA3)
SiemensSCALANCE M876-4 (EU) (6GK5876-4AA00-2BA2)
SiemensSCALANCE W721-1 RJ45 (6GK5721-1FC00-0AA0)
SiemensSCALANCE X308-2M PoE (6GK5308-2QG10-2AA2)
SiemensSIPLUS S7-1200 CPU 1215FC DC/DC/DC (6AG1215-1AF40-5XB0)
SiemensSIPLUS S7-1200 CPU 1214C DC/DC/DC RAIL (6AG2214-1AG40-1XB0)
SiemensSCALANCE W778-1 M12 EEC (6GK5778-1GY00-0TA0)
SiemensSCALANCE XR324-12M (230V, ports on rear) (6GK5324-0GG00-3HR2)
SiemensSCALANCE XR324-4M EEC (2x 100-240VAC/60-250VDC, ports on rear) (6GK5324-4GG00-4JR2)
SiemensSIMATIC S7-1200 CPU 1214C DC/DC/Rly (6ES7214-1HG40-0XB0)
SiemensSCALANCE W788-1 M12 (6GK5788-1GD00-0AA0)
SiemensRUGGEDCOM ROX RX1511
SiemensSCALANCE X302-7 EEC (230V, coated) (6GK5302-7GD00-3GA3)
SiemensSCALANCE XR324-4M EEC (24V, ports on front) (6GK5324-4GG10-1ER2)
SiemensSCALANCE W734-1 RJ45 (6GK5734-1FX00-0AB0)

…and 251 more

Timeline

References

Open in Interactive Console →