{"id":"GHSA-v5w6-wcm8-jm4q","revision":"18b4a14fa1074bb3b9cd0a7d921d68af","records":[{"revision":"18b4a14fa1074bb3b9cd0a7d921d68af","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"GHSA-v5w6-wcm8-jm4q","aliases":["CVE-2022-4450","RUSTSEC-2023-0010"],"title":"openssl-src contains Double free after calling `PEM_read_bio_ex`","description":"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.\n\nThe functions `PEM_read_bio()` and `PEM_read()` are simple wrappers around `PEM_read_bio_ex()` and therefore these functions are also directly affected.\n\nThese functions are also called indirectly by a number of other OpenSSL functions including `PEM_X509_INFO_read_bio_ex()` and\n`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.","state":0,"publishedAt":"2023-02-08T22:22:58+00:00","modifiedAt":"2026-09-10T03:49:52.1726836+00:00","affected":[{"ecosystem":"crates.io","name":"openssl-src","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"111.25.0"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"crates.io","name":"openssl-src","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"300.0.0"},{"kind":"fixed","version":"300.0.12"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"HIGH"}],"references":["https://nvd.nist.gov/vuln/detail/CVE-2022-4450","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://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003","https://rustsec.org/advisories/RUSTSEC-2023-0010.html","https://security.gentoo.org/glsa/202402-08","https://www.openssl.org/news/secadv/20230207.txt"],"sourceUrl":"https://github.com/advisories/GHSA-v5w6-wcm8-jm4q","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-v5w6-wcm8-jm4q","identifiers":["GHSA-v5w6-wcm8-jm4q","CVE-2022-4450","RUSTSEC-2023-0010"]},"retained":false,"historicalAffected":[]}],"coverage":[]}