ncat-7.93-1.1 on GA media SUSE Patch security@suse.de SUSE Security Team openSUSE-SU-2024:12303-1 Final 1 1 2024-06-15T00:00:00Z current 2024-06-15T00:00:00Z 2024-06-15T00:00:00Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z ncat-7.93-1.1 on GA media These are all security issues fixed in the ncat-7.93-1.1 package on the GA media of openSUSE Tumbleweed. The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). openSUSE-Tumbleweed-2024-12303 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/security/rating/ SUSE Security Ratings https://www.suse.com/security/cve/CVE-2021-3712/ SUSE CVE CVE-2021-3712 page openSUSE Tumbleweed ncat-7.93-1.1 nmap-7.93-1.1 nping-7.93-1.1 ncat-7.93-1.1 as a component of openSUSE Tumbleweed nmap-7.93-1.1 as a component of openSUSE Tumbleweed nping-7.93-1.1 as a component of openSUSE Tumbleweed 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). CVE-2021-3712 openSUSE Tumbleweed:ncat-7.93-1.1 openSUSE Tumbleweed:nmap-7.93-1.1 openSUSE Tumbleweed:nping-7.93-1.1 moderate 5.8 AV:N/AC:M/Au:N/C:P/I:N/A:P To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/security/cve/CVE-2021-3712.html CVE-2021-3712 https://bugzilla.suse.com/1189521 SUSE Bug 1189521 https://bugzilla.suse.com/1190129 SUSE Bug 1190129 https://bugzilla.suse.com/1191640 SUSE Bug 1191640 https://bugzilla.suse.com/1192100 SUSE Bug 1192100 https://bugzilla.suse.com/1192787 SUSE Bug 1192787 https://bugzilla.suse.com/1194948 SUSE Bug 1194948 https://bugzilla.suse.com/1225628 SUSE Bug 1225628