ReferencesĪSN.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. #OPENJDK 15 UPGRADE#Upgrade Debian:10 openssl to version 1.1.1d-0+deb10u8 or higher. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. #OPENJDK 15 VERIFICATION#In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. However any operation which requires the public key from the certificate will trigger the infinite loop. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Upgrade Debian:10 openssl to version 1.1.1n-0+deb10u3 or higher. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. This script is distributed by some operating systems in a manner where it is automatically executed. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. #OPENJDK 15 CODE#In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. Upgrade Debian:10 openssl to version 1.1.1d-0+deb10u7 or higher. The location of the buffer is application dependent but is typically heap allocated. 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. 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 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. 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. 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. Typically an application will call this function twice. In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). #OPENJDK 15 HOW TO#See How to fix? for Debian:10 relevant versions. Note: Versions mentioned in the description apply to the upstream openssl package.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |