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. 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. See How to fix? for Alpine:3.14 relevant fixed versions and status. Note: Versions mentioned in the description apply only to the upstream libretls package and not the libretls package as distributed by Alpine. Upgrade Alpine:3.14 zlib to version 1.2.12-r2 or higher. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference). NOTE: only applications that call inflateGetHeader are affected. Zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Alpine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |