{"id":"CVE-2022-4450","details":"The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and\ndecodes the \"name\" (e.g. \"CERTIFICATE\"), any header data and the payload data.\nIf the function succeeds then the \"name_out\", \"header\" and \"data\" arguments are\npopulated with pointers to buffers containing the relevant decoded data. The\ncaller is responsible for freeing those buffers. It is possible to construct a\nPEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex()\nwill return a failure code but will populate the header argument with a pointer\nto a buffer that has already been freed. If the caller also frees this buffer\nthen a double free will occur. This will most likely lead to a crash. This\ncould be exploited by an attacker who has the ability to supply malicious PEM\nfiles for parsing to achieve a denial of service attack.\n\nThe functions PEM_read_bio() and PEM_read() are simple wrappers around\nPEM_read_bio_ex() and therefore these functions are also directly affected.\n\nThese functions are also called indirectly by a number of other OpenSSL\nfunctions including PEM_X509_INFO_read_bio_ex() and\nSSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal\nuses of these functions are not vulnerable because the caller does not free the\nheader argument if PEM_read_bio_ex() returns a failure code. These locations\ninclude the PEM_read_bio_TYPE() functions as well as the decoders introduced in\nOpenSSL 3.0.\n\nThe OpenSSL asn1parse command line application is also impacted by this issue.","aliases":["GHSA-v5w6-wcm8-jm4q","RUSTSEC-2023-0010"],"modified":"2026-04-16T04:38:19.562051618Z","published":"2023-02-08T20:15:23.973Z","related":["ALSA-2023:0946","ALSA-2023:1405","ALSA-2023:2165","ALSA-2023:2932","CGA-wchx-98rm-h72v","SUSE-SU-2023:0309-1","SUSE-SU-2023:0310-1","SUSE-SU-2023:0311-1","SUSE-SU-2023:0312-1","openSUSE-SU-2024:12688-1","openSUSE-SU-2024:12716-1"],"references":[{"type":"WEB","url":"https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003"},{"type":"ADVISORY","url":"https://security.gentoo.org/glsa/202402-08"},{"type":"ADVISORY","url":"https://www.openssl.org/news/secadv/20230207.txt"},{"type":"FIX","url":"https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=63bcf189be73a9cc1264059bed6f57974be74a83"},{"type":"FIX","url":"https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=bbcf509bd046b34cca19c766bbddc31683d0858b"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/openssl/openssl","events":[{"introduced":"e04bd3433fd84e1861bf258ea37928d9845e6a86"},{"fixed":"e04bd3433fd84e1861bf258ea37928d9845e6a86"},{"introduced":"89cd17a031e022211684eb7eb41190cf1910f9fa"},{"fixed":"31157bc0b46e04227b8468d3e6915e4d0332777c"}],"database_specific":{"versions":[{"introduced":"1.1.1"},{"fixed":"1.1.1t"},{"introduced":"3.0.0"},{"fixed":"3.0.8"}]}}],"versions":["openssl-3.0.0","openssl-3.0.1","openssl-3.0.2","openssl-3.0.3","openssl-3.0.4","openssl-3.0.5","openssl-3.0.6","openssl-3.0.7"],"database_specific":{"vanir_signatures_modified":"2026-04-12T03:22:20Z","unresolved_ranges":[{"events":[{"introduced":"4.0.0"},{"fixed":"4.3.16"}]},{"events":[{"introduced":"4.4.0"},{"fixed":"4.6.3"}]}],"vanir_signatures":[{"id":"CVE-2022-4450-c377fa22","digest":{"line_hashes":["28170854778703993674264004058177114599","73132526844288570625317440636111911761","177405411499435185068645597737938634778","224809958623850711330610094965797758930","295554444428855106393106961197201359586"],"threshold":0.9},"signature_type":"Line","target":{"file":"include/openssl/opensslv.h"},"deprecated":false,"signature_version":"v1","source":"https://github.com/openssl/openssl/commit/e04bd3433fd84e1861bf258ea37928d9845e6a86"}],"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-4450.json"}}],"schema_version":"1.7.5","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"}]}