Double Free Affecting openssl-devel package, versions <1:3.0.1-47.el9_1
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-ALMALINUX9-OPENSSLDEVEL-5607601
- published 28 May 2023
- disclosed 28 Feb 2023
Introduced: 28 Feb 2023
CVE-2022-4450 Open this link in a new tabHow to fix?
Upgrade AlmaLinux:9 openssl-devel to version 1:3.0.1-47.el9_1 or higher.
This issue was patched in ALSA-2023:0946.
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl-devel package and not the openssl-devel package as distributed by AlmaLinux.
See How to fix? for AlmaLinux:9 relevant fixed versions and status.
The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack.
The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected.
These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0.
The OpenSSL asn1parse command line application is also impacted by this issue.
References
- https://errata.almalinux.org/9/ALSA-2023-0946.html
- https://errata.almalinux.org/8/ALSA-2023-1405.html
- https://errata.almalinux.org/9/ALSA-2023-2165.html
- https://errata.almalinux.org/8/ALSA-2023-2932.html
- https://access.redhat.com/security/cve/CVE-2022-4450
- https://access.redhat.com/errata/RHSA-2023:0946
- https://access.redhat.com/errata/RHSA-2023:1405
- https://access.redhat.com/errata/RHSA-2023:2165
- https://access.redhat.com/errata/RHSA-2023:2932
- https://www.openssl.org/news/secadv/20230207.txt
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=63bcf189be73a9cc1264059bed6f57974be74a83
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=bbcf509bd046b34cca19c766bbddc31683d0858b
- https://security.gentoo.org/glsa/202402-08