{"id":"CVE-2022-4450","aliases":["ALPINE-CVE-2022-4450","ALSA-2023:0946","ALSA-2023:1405","ALSA-2023:2165","ALSA-2023:2932","AZL-13347","AZL-13351","AZL-37629","AZL-37892","BELL-CVE-2022-4450","CLSA-2023-1680206329","CLSA-2023-1680210075","DEBIAN-CVE-2022-4450","DLA-3325-1","DSA-5343-1","EUVD-2023-0796","GHSA-v5w6-wcm8-jm4q","JLSEC-2026-232","MGASA-2023-0130","OESA-2023-1092","OESA-2023-1107","OESA-2023-1135","OESA-2023-1142","OESA-2024-2312","OESA-2024-2313","RHSA-2023:0946","RHSA-2023:1199","RHSA-2023:1405","RHSA-2023:2165","RHSA-2023:2932","RHSA-2023:3354","RHSA-2023:3408","RHSA-2023:3420","RLSA-2023:0946","RLSA-2023:1405","RUSTSEC-2023-0010","SUSE-SU-2023:0309-1","SUSE-SU-2023:0310-1","SUSE-SU-2023:0311-1","SUSE-SU-2023:0312-1","UBUNTU-CVE-2022-4450","USN-5844-1","USN-6564-1","USN-7894-1","openSUSE-SU-2024:12688-1","openSUSE-SU-2024:12716-1"],"status":"published","title":"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\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.","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.2859,"percentile":0.98149,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-415"],"published":"2023-02-07T00:00:00Z","modified":"2026-11-03T07:31:26Z","fixes":[{"ecosystem":"crates.io","package":"openssl-src","fixed_in":["111.25.0","300.0.12"],"sources":["ghsa","osv"]},{"ecosystem":"Alpine:v3.14","package":"openssl","fixed_in":["1.1.1t-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.15","package":"openssl","fixed_in":["1.1.1t-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.16","package":"openssl","fixed_in":["1.1.1t-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.17","package":"openssl","fixed_in":["3.0.8-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.18","package":"openssl","fixed_in":["3.0.8-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.19","package":"openssl","fixed_in":["3.0.8-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.20","package":"openssl","fixed_in":["3.0.8-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"openssl","fixed_in":["3.0.8-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"openssl","fixed_in":["3.0.8-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"openssl","fixed_in":["3.0.8-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"openssl","fixed_in":["3.0.8-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.17","package":"openssl1.1-compat","fixed_in":["1.1.1t-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.18","package":"openssl1.1-compat","fixed_in":["1.1.1t-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.15","package":"openssl3","fixed_in":["3.0.8-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.16","package":"openssl3","fixed_in":["3.0.8-r0"],"sources":["osv"]},{"ecosystem":"Azure Linux:2","package":"cloud-hypervisor","fixed_in":["30.0-2"],"sources":["osv"]},{"ecosystem":"Azure Linux:2","package":"openssl","fixed_in":["1.1.1k-21"],"sources":["osv"]},{"ecosystem":"Azure Linux:2","package":"hvloader","fixed_in":["1.0.1-2"],"sources":["osv"]},{"ecosystem":"Azure Linux:3","package":"hvloader","fixed_in":["1.0.1-4"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"openssl","fixed_in":["3.0.8-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"openssl","fixed_in":["3.0.8-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"openssl","fixed_in":["3.0.8-1"],"sources":["osv"]},{"ecosystem":"Julia","package":"OpenSSL_jll","fixed_in":["1.1.20+0"],"sources":["osv"]},{"ecosystem":"Julia","package":"Openresty_jll","fixed_in":["1.27.1+0"],"sources":["osv"]},{"ecosystem":"openEuler:22.03-LTS-SP3","package":"openresty-openssl111","fixed_in":["1.1.1h-4.oe2203sp3"],"sources":["osv"]},{"ecosystem":"openEuler:22.03-LTS-SP1","package":"openresty-openssl111","fixed_in":["1.1.1h-5.oe2203sp1"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"openssl","fixed_in":["1.1.1-1ubuntu2.1~18.04.21"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"openssl","fixed_in":["1.1.1-1ubuntu2.fips.2.1~18.04.21"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"openssl","fixed_in":["1.1.1f-1ubuntu2.17"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"openssl","fixed_in":["1.1.1f-1ubuntu2.fips.17"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"edk2","fixed_in":["2022.02-3ubuntu0.22.04.4"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"nodejs","fixed_in":["12.22.9~dfsg-1ubuntu3.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"openssl","fixed_in":["3.0.2-0ubuntu1.8"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"openssl-src","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"111.25.0"}]}]},{"source":"ghsa","ecosystem":"crates.io","package":"openssl-src","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"300.0.0"},{"fixed":"300.0.12"}]}]},{"source":"osv","ecosystem":"Alpine:v3.14","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1"},{"fixed":"1.1.1t-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.15","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1"},{"fixed":"1.1.1t-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.16","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1"},{"fixed":"1.1.1t-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.17","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.19","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.20","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.17","package":"openssl1.1-compat","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1t-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"openssl1.1-compat","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1t-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.15","package":"openssl3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.16","package":"openssl3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"AlmaLinux:9","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"AlmaLinux:9","package":"openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"AlmaLinux:9","package":"openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"AlmaLinux:9","package":"openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"AlmaLinux:8","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_7"}]}],"bundled":4},{"source":"osv","ecosystem":"AlmaLinux:8","package":"openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_7"}]}],"bundled":4},{"source":"osv","ecosystem":"AlmaLinux:8","package":"openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_7"}]}],"bundled":4},{"source":"osv","ecosystem":"AlmaLinux:8","package":"openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_7"}]}],"bundled":4},{"source":"osv","ecosystem":"AlmaLinux:9","package":"edk2-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20221207gitfff6d81270b5-9.el9_2"}]}],"bundled":5},{"source":"osv","ecosystem":"AlmaLinux:9","package":"edk2-ovmf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20221207gitfff6d81270b5-9.el9_2"}]}],"bundled":5},{"source":"osv","ecosystem":"AlmaLinux:9","package":"edk2-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20221207gitfff6d81270b5-9.el9_2"}]}],"bundled":5},{"source":"osv","ecosystem":"AlmaLinux:9","package":"edk2-tools-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20221207gitfff6d81270b5-9.el9_2"}]}],"bundled":5},{"source":"osv","ecosystem":"AlmaLinux:8","package":"edk2-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20220126gitbb1bba3d77-4.el8"}]}],"bundled":4},{"source":"osv","ecosystem":"AlmaLinux:8","package":"edk2-ovmf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20220126gitbb1bba3d77-4.el8"}]}],"bundled":4},{"source":"osv","ecosystem":"Azure Linux:2","package":"cloud-hypervisor","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"30.0-2"}]}]},{"source":"osv","ecosystem":"Azure Linux:2","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1k-21"}]}]},{"source":"osv","ecosystem":"Azure Linux:2","package":"hvloader","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.1-2"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"hvloader","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.1-4"}]}]},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-15.el8.4.tuxcare.els6"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-15.el8.4.tuxcare.els6"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-15.el8.4.tuxcare.els6"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-15.el8.4.tuxcare.els6"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:CentOS:8.4","package":"openssl-static","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-15.el8.4.tuxcare.els6"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-5.el8.5.tuxcare.els5"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-5.el8.5.tuxcare.els5"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-5.el8.5.tuxcare.els5"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-5.el8.5.tuxcare.els5"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:CentOS:8.5","package":"openssl-static","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-5.el8.5.tuxcare.els5"}]}],"bundled":2},{"source":"osv","ecosystem":"Debian:12","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.8-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.8-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.8-1"}]}]},{"source":"osv","ecosystem":"Debian:10","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1n-0+deb10u4"}]}],"versions":["1.1.1c-1","1.1.1d-0+deb10u1","1.1.1d-0+deb10u2","1.1.1d-0+deb10u3","1.1.1d-0+deb10u4","1.1.1d-0+deb10u5","1.1.1d-0+deb10u6","1.1.1d-0+deb10u7","1.1.1d-0+deb10u8","1.1.1d-1","1.1.1d-2","1.1.1e-1","1.1.1f-1","1.1.1g-1","1.1.1h-1","1.1.1i-1","1.1.1i-2","1.1.1i-3","1.1.1j-1","1.1.1k-1","1.1.1l-1","1.1.1m-1","1.1.1n-0+deb10u1","1.1.1n-0+deb10u2","1.1.1n-0+deb10u3"],"bundled":5},{"source":"osv","ecosystem":"Debian:11","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1n-0+deb11u4"}]}],"versions":["1.1.1k-1","1.1.1k-1+deb11u1","1.1.1k-1+deb11u2","1.1.1l-1","1.1.1m-0+deb11u1","1.1.1m-1","1.1.1n-0+deb11u1","1.1.1n-0+deb11u2","1.1.1n-0+deb11u3"],"bundled":5},{"source":"osv","ecosystem":"crates.io","package":"openssl-src","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"111.25.0"}]}]},{"source":"osv","ecosystem":"crates.io","package":"openssl-src","ranges":[{"type":"SEMVER","events":[{"introduced":"300.0.0"},{"fixed":"300.0.12"}]}]},{"source":"osv","ecosystem":"Julia","package":"OpenSSL_jll","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.1.20+0"}]}]},{"source":"osv","ecosystem":"Julia","package":"Openresty_jll","ranges":[{"type":"SEMVER","events":[{"introduced":"1.19.9+0"},{"fixed":"1.27.1+0"}]}]},{"source":"osv","ecosystem":"Mageia:8","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1t-1.mga8"}]}],"bundled":11},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP1","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1f-22.oe1"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP3","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1f-22.oe1"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:22.03-LTS","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1m-18.oe2203"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1m-16.oe2203sp1"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP1","package":"edk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"202002-15.oe1"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP3","package":"edk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"202002-15.oe1"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:22.03-LTS","package":"edk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"202011-11.oe2203sp1"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"edk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"202011-11.oe2203sp1"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP1","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.11-3.oe1"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP3","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.11-3.oe1"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:22.03-LTS","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.11-4.oe2203sp1"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.11-4.oe2203sp1"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"openresty-openssl111","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1h-4.oe2203sp3"}]}]},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"openresty-openssl111","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1h-5.oe2203sp1"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-libs-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl-libs-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.0::appstream","package":"openssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-46.el9_0"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.0::appstream","package":"openssl-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-46.el9_0"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.0::appstream","package":"openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-46.el9_0"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.0::appstream","package":"openssl-libs-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-46.el9_0"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.0::appstream","package":"openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-46.el9_0"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.0::baseos","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-46.el9_0"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.0::baseos","package":"openssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-46.el9_0"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.0::baseos","package":"openssl-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-46.el9_0"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.0::baseos","package":"openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-46.el9_0"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.0::baseos","package":"openssl-libs-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-46.el9_0"}]}],"bundled":8},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_7"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_7"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_7"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_7"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_7"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl-libs-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_7"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_7"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"edk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:20221207gitfff6d81270b5-9.el9_2"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"edk2-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:20221207gitfff6d81270b5-9.el9_2"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"edk2-ovmf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:20221207gitfff6d81270b5-9.el9_2"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"edk2-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:20221207gitfff6d81270b5-9.el9_2"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"edk2-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:20221207gitfff6d81270b5-9.el9_2"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"edk2-ovmf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:20221207gitfff6d81270b5-9.el9_2"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"edk2-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:20221207gitfff6d81270b5-9.el9_2"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"edk2-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:20221207gitfff6d81270b5-9.el9_2"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::crb","package":"edk2-tools-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:20221207gitfff6d81270b5-9.el9_2"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::appstream","package":"edk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:20220126gitbb1bba3d77-4.el8"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::appstream","package":"edk2-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:20220126gitbb1bba3d77-4.el8"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::appstream","package":"edk2-ovmf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:20220126gitbb1bba3d77-4.el8"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-httpd","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-httpd-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-httpd-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-httpd-manual","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-httpd-selinux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-httpd-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_ldap","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_proxy_html","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.4.51-39.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_session","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_ssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.4.51-39.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-httpd","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-httpd-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-httpd-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-httpd-manual","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-httpd-selinux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-httpd-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-httpd-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-mod_ldap","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-mod_ldap-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-mod_proxy_html","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-mod_proxy_html-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-mod_session","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-mod_session-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-mod_ssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-mod_ssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.4.51-39.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-14.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-14.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-14.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-14.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-14.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-static","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-14.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-14.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-openssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-14.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-14.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-14.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-openssl-libs-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-14.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-14.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-openssl-static","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-14.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-apr-util","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-apr-util-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-apr-util-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-apr-util-ldap","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-apr-util-mysql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-apr-util-nss","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-apr-util-odbc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-apr-util-openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-apr-util-pgsql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-apr-util-sqlite","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-ldap","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-ldap-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-mysql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-mysql-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-nss","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-nss-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-odbc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-odbc-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-openssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-pgsql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-pgsql-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-sqlite","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-apr-util-sqlite-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.6.1-101.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.1-1.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-curl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.1-1.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-libcurl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.1-1.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-libcurl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.1-1.el7jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.1-1.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-curl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.1-1.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-libcurl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.1-1.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-libcurl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.1-1.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el8","package":"jbcs-httpd24-libcurl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.1-1.el8jbcs"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.6::baseos","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_6"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.6::baseos","package":"openssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_6"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.6::baseos","package":"openssl-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_6"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.6::baseos","package":"openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_6"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.6::baseos","package":"openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_6"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.6::baseos","package":"openssl-libs-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_6"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.6::baseos","package":"openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_6"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:jboss_enterprise_web_server:5.7::el7","package":"jws5-tomcat-native","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.31-14.redhat_14.el7jws"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:jboss_enterprise_web_server:5.7::el7","package":"jws5-tomcat-native-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.31-14.redhat_14.el7jws"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:jboss_enterprise_web_server:5.7::el8","package":"jws5-tomcat-native","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.31-14.redhat_14.el8jws"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:jboss_enterprise_web_server:5.7::el8","package":"jws5-tomcat-native-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.31-14.redhat_14.el8jws"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:jboss_enterprise_web_server:5.7::el9","package":"jws5-tomcat-native","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.31-14.redhat_14.el9jws"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:jboss_enterprise_web_server:5.7::el9","package":"jws5-tomcat-native-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.31-14.redhat_14.el9jws"}]}],"bundled":4},{"source":"osv","ecosystem":"Rocky Linux:9","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"Rocky Linux:8","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1k-9.el8_7"}]}],"bundled":4},{"source":"osv","ecosystem":"crates.io","package":"openssl-src","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"111.25.0"},{"introduced":"300.0.0"},{"fixed":"300.0.12"}]}]},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud 9","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-2.75.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud Crowbar 9","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-2.75.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP4","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-2.75.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP5","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-2.75.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP4-LTSS","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-2.75.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-2.75.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-2.75.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Real Time 15 SP3","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.2","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Manager Retail Branch Server 4.2","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Manager Server 4.2","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.2","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1d-150200.11.57.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1l-150400.7.22.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP4","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1l-150400.7.22.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap Micro 5.3","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1l-150400.7.22.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.4","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1l-150400.7.22.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP4","package":"openssl-3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.1-150400.4.17.1"}]}],"bundled":8},{"source":"osv","ecosystem":"openSUSE:Leap 15.4","package":"openssl-3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.1-150400.4.17.1"}]}],"bundled":8},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"edk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0~20150106.5c2d456b-2","0~20160104.c2a892d7-1","0~20160408.ffea0a2c-2","0~20160408.ffea0a2c-2ubuntu0.1","0~20160408.ffea0a2c-2ubuntu0.2","0~20160408.ffea0a2c-2ubuntu0.2+esm1","0~20160408.ffea0a2c-2ubuntu0.2+esm3","0~20160408.ffea0a2c-2ubuntu0.2+esm4"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1-1ubuntu2.1~18.04.21"}]}],"versions":["1.0.2g-1ubuntu13","1.0.2g-1ubuntu14","1.0.2n-1ubuntu1","1.1.0g-2ubuntu1","1.1.0g-2ubuntu2","1.1.0g-2ubuntu3","1.1.0g-2ubuntu4","1.1.0g-2ubuntu4.1","1.1.0g-2ubuntu4.3","1.1.1-1ubuntu2.1~18.04.1","1.1.1-1ubuntu2.1~18.04.2","1.1.1-1ubuntu2.1~18.04.3","1.1.1-1ubuntu2.1~18.04.4","1.1.1-1ubuntu2.1~18.04.5","1.1.1-1ubuntu2.1~18.04.6","1.1.1-1ubuntu2.1~18.04.7","1.1.1-1ubuntu2.1~18.04.8","1.1.1-1ubuntu2.1~18.04.9","1.1.1-1ubuntu2.1~18.04.10","1.1.1-1ubuntu2.1~18.04.13","1.1.1-1ubuntu2.1~18.04.14","1.1.1-1ubuntu2.1~18.04.15","1.1.1-1ubuntu2.1~18.04.17","1.1.1-1ubuntu2.1~18.04.19","1.1.1-1ubuntu2.1~18.04.20"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"edk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0~20170911.5dfba97c-1","0~20171010.234dbcef-1","0~20171027.76fd5a66-1","0~20171205.a9212288-1","0~20180105.0bc94c74-1","0~20180205.c0d9813c-1","0~20180205.c0d9813c-2","0~20180205.c0d9813c-2ubuntu0.1","0~20180205.c0d9813c-2ubuntu0.2","0~20180205.c0d9813c-2ubuntu0.3","0~20180205.c0d9813c-2ubuntu0.3+esm1","0~20180205.c0d9813c-2ubuntu0.3+esm2","0~20180205.c0d9813c-2ubuntu0.3+esm3"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1-1ubuntu2.fips.2.1~18.04.21"}]}],"versions":["1.1.1-1ubuntu2.fips.2.1~18.04.5.1","1.1.1-1ubuntu2.fips.2.1~18.04.6.1","1.1.1-1ubuntu2.fips.2.1~18.04.7.1","1.1.1-1ubuntu2.fips.2.1~18.04.9.1","1.1.1-1ubuntu2.fips.2.1~18.04.9.2","1.1.1-1ubuntu2.fips.2.1~18.04.9.3","1.1.1-1ubuntu2.fips.2.1~18.04.13.2","1.1.1-1ubuntu2.fips.2.1~18.04.15","1.1.1-1ubuntu2.fips.2.1~18.04.15.1","1.1.1-1ubuntu2.fips.2.1~18.04.15.2","1.1.1-1ubuntu2.fips.2.1~18.04.17","1.1.1-1ubuntu2.fips.2.1~18.04.20"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.1.1-1ubuntu2.fips.2.1~18.04.3.1","1.1.1-1ubuntu2.fips.2.1~18.04.15.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1f-1ubuntu2.17"}]}],"versions":["1.1.1c-1ubuntu4","1.1.1d-2ubuntu3","1.1.1d-2ubuntu6","1.1.1f-1ubuntu1","1.1.1f-1ubuntu2","1.1.1f-1ubuntu2.1","1.1.1f-1ubuntu2.2","1.1.1f-1ubuntu2.3","1.1.1f-1ubuntu2.4","1.1.1f-1ubuntu2.5","1.1.1f-1ubuntu2.8","1.1.1f-1ubuntu2.9","1.1.1f-1ubuntu2.10","1.1.1f-1ubuntu2.11","1.1.1f-1ubuntu2.12","1.1.1f-1ubuntu2.13","1.1.1f-1ubuntu2.15","1.1.1f-1ubuntu2.16"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"edk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0~20190606.20d2e5a1-2ubuntu1","0~20190828.37eef910-3","0~20190828.37eef910-4","0~20191122.bd85bf54-1","0~20191122.bd85bf54-1ubuntu1","0~20191122.bd85bf54-2","0~20191122.bd85bf54-2ubuntu1","0~20191122.bd85bf54-2ubuntu2","0~20191122.bd85bf54-2ubuntu3","0~20191122.bd85bf54-2ubuntu3.1","0~20191122.bd85bf54-2ubuntu3.2","0~20191122.bd85bf54-2ubuntu3.3","0~20191122.bd85bf54-2ubuntu3.4","0~20191122.bd85bf54-2ubuntu3.5","0~20191122.bd85bf54-2ubuntu3.6","0~20191122.bd85bf54-2ubuntu3.6+esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1f-1ubuntu2.fips.17"}]}],"versions":["1.1.1f-1ubuntu2.fips.7","1.1.1f-1ubuntu2.fips.7.2","1.1.1f-1ubuntu2.fips.12","1.1.1f-1ubuntu2.fips.13","1.1.1f-1ubuntu2.fips.13.1","1.1.1f-1ubuntu2.fips.16"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.1.1f-1ubuntu2.fips.2.8","1.1.1f-1ubuntu2.fips.7.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"edk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2022.02-3ubuntu0.22.04.4"}]}],"versions":["2021.08~rc0-2","2021.08-3","2021.11~rc1-1","2021.11-1","2021.11-2","2022.02~rc1-1","2022.02~rc1-1ubuntu1","2022.02-1","2022.02-2","2022.02-3","2022.02-3ubuntu0.22.04.1","2022.02-3ubuntu0.22.04.2","2022.02-3ubuntu0.22.04.3"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.9~dfsg-1ubuntu3.3"}]}],"versions":["12.22.5~dfsg-5ubuntu1","12.22.7~dfsg-2ubuntu1","12.22.7~dfsg-2ubuntu3","12.22.9~dfsg-1ubuntu2","12.22.9~dfsg-1ubuntu3","12.22.9~dfsg-1ubuntu3.1","12.22.9~dfsg-1ubuntu3.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.2-0ubuntu1.8"}]}],"versions":["1.1.1l-1ubuntu1","3.0.0-1ubuntu1","3.0.1-0ubuntu1","3.0.2-0ubuntu1","3.0.2-0ubuntu1.1","3.0.2-0ubuntu1.2","3.0.2-0ubuntu1.4","3.0.2-0ubuntu1.5","3.0.2-0ubuntu1.6","3.0.2-0ubuntu1.7"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1-1ubuntu2.1~18.04.21"}]}],"versions":["1.0.2g-1ubuntu13","1.0.2g-1ubuntu14","1.0.2n-1ubuntu1","1.1.0g-2ubuntu1","1.1.0g-2ubuntu2","1.1.0g-2ubuntu3","1.1.0g-2ubuntu4","1.1.0g-2ubuntu4.1","1.1.0g-2ubuntu4.3","1.1.1-1ubuntu2.1~18.04.1","1.1.1-1ubuntu2.1~18.04.2","1.1.1-1ubuntu2.1~18.04.3","1.1.1-1ubuntu2.1~18.04.4","1.1.1-1ubuntu2.1~18.04.5","1.1.1-1ubuntu2.1~18.04.6","1.1.1-1ubuntu2.1~18.04.7","1.1.1-1ubuntu2.1~18.04.8","1.1.1-1ubuntu2.1~18.04.9","1.1.1-1ubuntu2.1~18.04.10","1.1.1-1ubuntu2.1~18.04.13","1.1.1-1ubuntu2.1~18.04.14","1.1.1-1ubuntu2.1~18.04.15","1.1.1-1ubuntu2.1~18.04.17","1.1.1-1ubuntu2.1~18.04.19","1.1.1-1ubuntu2.1~18.04.20"],"bundled":8},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1f-1ubuntu2.17"}]}],"versions":["1.1.1c-1ubuntu4","1.1.1d-2ubuntu3","1.1.1d-2ubuntu6","1.1.1f-1ubuntu1","1.1.1f-1ubuntu2","1.1.1f-1ubuntu2.1","1.1.1f-1ubuntu2.2","1.1.1f-1ubuntu2.3","1.1.1f-1ubuntu2.4","1.1.1f-1ubuntu2.5","1.1.1f-1ubuntu2.8","1.1.1f-1ubuntu2.9","1.1.1f-1ubuntu2.10","1.1.1f-1ubuntu2.11","1.1.1f-1ubuntu2.12","1.1.1f-1ubuntu2.13","1.1.1f-1ubuntu2.15","1.1.1f-1ubuntu2.16"],"bundled":8},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.2-0ubuntu1.8"}]}],"versions":["1.1.1l-1ubuntu1","3.0.0-1ubuntu1","3.0.1-0ubuntu1","3.0.2-0ubuntu1","3.0.2-0ubuntu1.1","3.0.2-0ubuntu1.2","3.0.2-0ubuntu1.4","3.0.2-0ubuntu1.5","3.0.2-0ubuntu1.6","3.0.2-0ubuntu1.7"],"bundled":8},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.9~dfsg-1ubuntu3.3"}]}],"versions":["12.22.5~dfsg-5ubuntu1","12.22.7~dfsg-2ubuntu1","12.22.7~dfsg-2ubuntu3","12.22.9~dfsg-1ubuntu2","12.22.9~dfsg-1ubuntu3","12.22.9~dfsg-1ubuntu3.1","12.22.9~dfsg-1ubuntu3.2"],"bundled":5},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"edk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2022.02-3ubuntu0.22.04.4"}]}],"versions":["2021.08~rc0-2","2021.08-3","2021.11~rc1-1","2021.11-1","2021.11-2","2022.02~rc1-1","2022.02~rc1-1ubuntu1","2022.02-1","2022.02-2","2022.02-3","2022.02-3ubuntu0.22.04.1","2022.02-3ubuntu0.22.04.2","2022.02-3ubuntu0.22.04.3"],"bundled":30},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"edk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2024.02-2ubuntu0.6"}]}],"versions":["2023.05-2","2023.11-2","2023.11-3","2023.11-4","2023.11-5","2023.11-6","2023.11-8","2024.02-1","2024.02-2","2024.02-2ubuntu0.1","2024.02-2ubuntu0.3","2024.02-2ubuntu0.4","2024.02-2ubuntu0.5"],"bundled":30},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1t-1.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"openssl-3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.8-1.1"}]}],"bundled":8}],"products":[{"vendor":"openssl","product":"openssl"},{"vendor":"siemens","product":"scalance w1750d (jp)"},{"vendor":"siemens","product":"scalance w1750d (row)"},{"vendor":"siemens","product":"scalance w1750d (usa)"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518-4 pn/dp mfp"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518f-4 pn/dp mfp"},{"vendor":"siemens","product":"simatic s7-1500 tm mfp - gnu/linux subsystem"},{"vendor":"siemens","product":"siplus s7-1500 cpu 1518-4 pn/dp mfp"},{"vendor":"stormshield","product":"stormshield_network_security"}],"references":[{"url":"https://www.openssl.org/news/secadv/20230207.txt","tags":["vendor-advisory","x_transferred","Vendor Advisory","advisory","web","article","report"]},{"url":"https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=63bcf189be73a9cc1264059bed6f57974be74a83","tags":["patch","x_transferred","Patch","Vendor Advisory","fix","web"]},{"url":"https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=bbcf509bd046b34cca19c766bbddc31683d0858b","tags":["patch","x_transferred","Patch","Vendor Advisory","fix","web"]},{"url":"https://security.gentoo.org/glsa/202402-08","tags":["x_transferred","advisory","web"]},{"url":"https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-203374.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-794697.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-561322.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-699386.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-398330.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-943925.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-556635.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-879734.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-625862.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-337522.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-769027.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-4450","tags":["web","advisory"]},{"url":"https://rustsec.org/advisories/RUSTSEC-2023-0010.html","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-v5w6-wcm8-jm4q","tags":["web"]},{"url":"https://security.alpinelinux.org/vuln/CVE-2022-4450","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2023:0946","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-4203","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-4304","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-4450","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-0215","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-0216","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-0217","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-0286","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-0401","tags":["report"]},{"url":"https://bugzilla.redhat.com/2164440","tags":["report"]},{"url":"https://bugzilla.redhat.com/2164487","tags":["report"]},{"url":"https://bugzilla.redhat.com/2164488","tags":["report"]},{"url":"https://bugzilla.redhat.com/2164492","tags":["report"]},{"url":"https://bugzilla.redhat.com/2164494","tags":["report"]},{"url":"https://bugzilla.redhat.com/2164497","tags":["report"]},{"url":"https://bugzilla.redhat.com/2164499","tags":["report"]},{"url":"https://bugzilla.redhat.com/2164500","tags":["report"]},{"url":"https://errata.almalinux.org/9/ALSA-2023-0946.html","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2023:1405","tags":["advisory","web"]},{"url":"https://errata.almalinux.org/8/ALSA-2023-1405.html","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2023:2165","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-38578","tags":["report"]},{"url":"https://bugzilla.redhat.com/1960321","tags":["report"]},{"url":"https://errata.almalinux.org/9/ALSA-2023-2165.html","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2023:2932","tags":["advisory"]},{"url":"https://errata.almalinux.org/8/ALSA-2023-2932.html","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2022-4450","tags":["advisory"]},{"url":"https://errata.cloudlinux.com/centos8.4-els/CLSA-2023-1680206329.html","tags":["advisory"]},{"url":"https://errata.cloudlinux.com/centos8.5-els/CLSA-2023-1680210075.html","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/4xxx/CVE-2022-4450.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2022-4450","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2023-0130.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=31526","tags":["report"]},{"url":"https://www.debian.org/security/2023/dsa-5343","tags":["web"]},{"url":"https://ubuntu.com/security/notices/USN-5844-1","tags":["advisory"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/thread/RGMDA2QI6RIJSJF3FDWES76ORE53ELXX/","tags":["web"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/thread/MGJS3DWIQT3W4V6WXNE2IHFLOKIFL22G/","tags":["web"]},{"url":"https://www.openssl.org/news/secadv/20230322.txt","tags":["web"]},{"url":"https://www.openssl.org/news/secadv/20230328.txt","tags":["web"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1092","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-0215","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-4304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-0286","tags":["advisory"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1107","tags":["advisory"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1135","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-0401","tags":["advisory"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1142","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2312","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2313","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#important","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144000","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144003","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144006","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144008","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144010","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144012","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144015","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144017","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144019","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2145170","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2158412","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2164440","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2164487","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2164488","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2164492","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2164494","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2164497","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2164499","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2164500","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2023/rhsa-2023_0946.json","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-4203","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-4203","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-4304","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-4450","tags":["advisory","report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-0215","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-0216","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-0216","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-0217","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-0217","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-0286","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-0401","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2023:1199","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144001","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144004","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144007","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144009","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144011","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144013","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144016","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144018","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144020","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2145171","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2158413","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2023/rhsa-2023_1199.json","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2023/rhsa-2023_1405.json","tags":["advisory"]},{"url":"https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.2_release_notes/index","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1960321","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1983086","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2125336","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2132951","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2157656","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2162307","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2168046","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2174605","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2023/rhsa-2023_2165.json","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-38578","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-38578","tags":["advisory"]},{"url":"https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.8_release_notes/index","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2023/rhsa-2023_2932.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2023:3354","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2152639","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2152652","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2161774","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2167797","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2167813","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2167815","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2169652","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2176209","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2179062","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2179069","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2023/rhsa-2023_3354.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2006-20001","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2006-20001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2006-20001","tags":["advisory"]},{"url":"https://httpd.apache.org/security/vulnerabilities_24.html#CVE-2006-20001","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-25147","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-25147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-25147","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-43551","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-43551","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-43551","tags":["advisory"]},{"url":"https://curl.se/docs/CVE-2022-43551.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-43552","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-43552","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-43552","tags":["advisory"]},{"url":"https://curl.se/docs/CVE-2022-43552.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-23914","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-23914","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-23914","tags":["advisory"]},{"url":"https://curl.se/docs/CVE-2023-23914.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-23915","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-23915","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-23915","tags":["advisory"]},{"url":"https://curl.se/docs/CVE-2023-23915.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-23916","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-23916","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-23916","tags":["advisory"]},{"url":"https://curl.se/docs/CVE-2023-23916.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-25690","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-25690","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-25690","tags":["advisory"]},{"url":"https://httpd.apache.org/security/vulnerabilities_24.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-27533","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-27533","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-27533","tags":["advisory"]},{"url":"https://curl.se/docs/CVE-2023-27533.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-27534","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-27534","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-27534","tags":["advisory"]},{"url":"https://curl.se/docs/CVE-2023-27534.html","tags":["article"]},{"url":"https://access.redhat.com/errata/RHSA-2023:3408","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#moderate","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2023/rhsa-2023_3408.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2023:3420","tags":["advisory"]},{"url":"https://issues.redhat.com/browse/JWS-2933","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2023/rhsa-2023_3420.json","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2023:0946","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2023:1405","tags":["advisory"]},{"url":"https://crates.io/crates/openssl-src","tags":["package"]},{"url":"https://www.suse.com/support/update/announcement/2023/suse-su-20230309-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1207533","tags":["report"]},{"url":"https://bugzilla.suse.com/1207534","tags":["report"]},{"url":"https://bugzilla.suse.com/1207536","tags":["report"]},{"url":"https://bugzilla.suse.com/1207538","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-4304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-4450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-0215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-0286","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2023/suse-su-20230310-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1121365","tags":["report"]},{"url":"https://bugzilla.suse.com/1198472","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2023/suse-su-20230311-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2023/suse-su-20230312-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1195149","tags":["report"]},{"url":"https://bugzilla.suse.com/1206222","tags":["report"]},{"url":"https://bugzilla.suse.com/1207535","tags":["report"]},{"url":"https://bugzilla.suse.com/1207539","tags":["report"]},{"url":"https://bugzilla.suse.com/1207540","tags":["report"]},{"url":"https://bugzilla.suse.com/1207541","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-4203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-0216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-0217","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-0401","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2022-4450","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-6564-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7894-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2022-4203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-4304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-0215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-0216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-0217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-0286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-0401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-3712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-0778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-0464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-0465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-0466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-2650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-3446","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-3817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-5678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-6237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-45236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-45237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-0727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-1298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-2511","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-4741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-5535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-6119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-9143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-13176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-38805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-2295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-3770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-9232","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2022-4450","title":"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\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.","status":"published","published":"2023-02-08T19:04:04.874Z","modified":"2026-10-14T14:39:44.108Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"adp"}],"cwes":["CWE-415"],"updated_at":"2026-11-02T14:34:37.932195Z"}],"euvd":[{"id":"EUVD-2023-0796","description":"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.","status":"published","published":"2023-02-08T19:04:04Z","modified":"2026-10-14T14:39:44Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T17:27:15.108271Z"}],"ghsa":[{"id":"GHSA-v5w6-wcm8-jm4q","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.","status":"published","published":"2023-02-08T22:22:58Z","modified":"2025-11-04T22:08:19Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-415"],"updated_at":"2026-11-02T14:39:06.376137Z"}],"nvd":[{"id":"CVE-2022-4450","description":"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.","status":"published","published":"2023-02-08T20:15:23.973Z","modified":"2026-10-14T15:17:00.197Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"primary"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"secondary"}],"cwes":["CWE-415"],"updated_at":"2026-11-02T14:07:36.026349Z"}],"osv":[{"id":"ALPINE-CVE-2022-4450","description":"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.","status":"published","published":"2023-02-08T20:15:23.973Z","modified":"2026-11-03T07:31:26.10737854Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-03T07:50:01.054176Z"},{"id":"AZL-13347","title":"CVE-2022-4450 affecting package cloud-hypervisor for versions less than 30.0-2","description":"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.","status":"published","published":"2023-02-08T20:15:23Z","modified":"2026-04-21T04:22:48.355173Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:02.666535Z"},{"id":"AZL-13351","title":"CVE-2022-4450 affecting package openssl for versions less than 1.1.1k-21","description":"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.","status":"published","published":"2023-02-08T20:15:23Z","modified":"2026-04-21T04:22:49.725688Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:02.666535Z"},{"id":"AZL-37629","title":"CVE-2022-4450 affecting package hvloader for versions less than 1.0.1-2","description":"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.","status":"published","published":"2023-02-08T20:15:23Z","modified":"2026-04-21T04:28:22.881633Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:04.608733Z"},{"id":"AZL-37892","title":"CVE-2022-4450 affecting package hvloader for versions less than 1.0.1-4","description":"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.","status":"published","published":"2023-02-08T20:15:23Z","modified":"2026-04-21T04:56:15.155748Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:04.608733Z"},{"id":"BELL-CVE-2022-4450","title":"CVE-2022-4450 does not affect BellSoft software","status":"withdrawn","published":"2023-08-31T12:13:41.6776Z","modified":"2026-01-26T09:46:14.685256Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:17.151188Z"},{"id":"CVE-2022-4450","title":"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\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.","status":"published","published":"2023-02-08T19:04:04.874Z","modified":"2026-10-28T10:31:01.514465813Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:27.481647Z"},{"id":"GHSA-v5w6-wcm8-jm4q","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.","status":"published","published":"2023-02-08T22:22:58Z","modified":"2026-09-10T03:49:52.172683553Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-415"],"updated_at":"2026-11-02T15:46:56.639206Z"},{"id":"JLSEC-2026-232","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\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\n`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\nfunctions including `PEM_X509_INFO_read_bio_ex()` and\n`SSL_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.","status":"published","published":"2026-04-27T18:33:55.942Z","modified":"2026-07-25T18:24:07.475720188Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:47:18.573531Z"},{"id":"OESA-2023-1092","title":"openssl security update","description":"OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.\r\n\r\nSecurity Fix(es):\r\n\r\nThe public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL cms and smime command line applications are similarly affected.(CVE-2023-0215)\r\n\r\nA timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.(CVE-2022-4304)\r\n\r\nThe function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the \u0026quot;name\u0026quot; (e.g. \u0026quot;CERTIFICATE\u0026quot;), any header data and the payload data. If the function succeeds then the \u0026quot;name_out\u0026quot;, \u0026quot;header\u0026quot; and \u0026quot;data\u0026quot; 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.(CVE-2022-4450)\n\nThere is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.(CVE-2023-0286)","status":"published","published":"2023-02-17T11:05:34Z","modified":"2026-08-18T01:17:30.828104849Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:39.934788Z"},{"id":"OESA-2023-1107","title":"openssl security update","description":"\r\n\r\nSecurity Fix(es):\r\n\r\nThe public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL cms and smime command line applications are similarly affected.(CVE-2023-0215)\r\n\r\nA timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.(CVE-2022-4304)\r\n\r\nThe function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the \u0026quot;name\u0026quot; (e.g. \u0026quot;CERTIFICATE\u0026quot;), any header data and the payload data. If the function succeeds then the \u0026quot;name_out\u0026quot;, \u0026quot;header\u0026quot; and \u0026quot;data\u0026quot; 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.(CVE-2022-4450)\n\nThere is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.(CVE-2023-0286)","status":"published","published":"2023-02-21T11:05:35Z","modified":"2026-08-18T01:17:37.263903201Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:52:39.934788Z"},{"id":"OESA-2023-1135","title":"edk2 security update","description":"EDK II is a modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications. \r\n\r\nSecurity Fix(es):\r\n\r\nThe public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL cms and smime command line applications are similarly affected.(CVE-2023-0215)\r\n\r\nThere is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.(CVE-2023-0286)\r\n\r\nA NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initialization will fail. There is a missing check for the return value from the initialization function which later leads to invalid usage of the digest API most likely leading to a crash. The unavailability of an algorithm can be caused by using FIPS enabled configuration of providers or more commonly by not loading the legacy provider. PKCS7 data is processed by the SMIME library calls and also by the time stamp (TS) library calls. The TLS implementation in OpenSSL does not call these functions however third party applications would be affected if they call these functions to verify signatures on untrusted data.(CVE-2023-0401)\r\n\r\nThe function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the \u0026quot;name\u0026quot; (e.g. \u0026quot;CERTIFICATE\u0026quot;), any header data and the payload data. If the function succeeds then the \u0026quot;name_out\u0026quot;, \u0026quot;header\u0026quot; and \u0026quot;data\u0026quot; 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.(CVE-2022-4450)","status":"published","published":"2023-03-04T11:05:36Z","modified":"2026-08-18T01:17:31.817513043Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:39.934788Z"},{"id":"OESA-2023-1142","title":"nodejs security update","description":"Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.\r\n\r\nSecurity Fix(es):\r\n\r\nThe public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL cms and smime command line applications are similarly affected.(CVE-2023-0215)\r\n\r\nThere is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.(CVE-2023-0286)\r\n\r\nA timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.(CVE-2022-4304)\r\n\r\nThe function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the \u0026quot;name\u0026quot; (e.g. \u0026quot;CERTIFICATE\u0026quot;), any header data and the payload data. If the function succeeds then the \u0026quot;name_out\u0026quot;, \u0026quot;header\u0026quot; and \u0026quot;data\u0026quot; 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.(CVE-2022-4450)","status":"published","published":"2023-03-04T11:05:37Z","modified":"2026-08-18T01:17:38.752206208Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:39.934788Z"},{"id":"OESA-2024-2312","title":"openresty-openssl111 security update","description":"Security Fix(es):\r\n\r\nThe function PEM_read_bio_ex() reads a PEM file from a BIO and parses and\ndecodes the \u0026quot;name\u0026quot; (e.g. \u0026quot;CERTIFICATE\u0026quot;), any header data and the payload data.\nIf the function succeeds then the \u0026quot;name_out\u0026quot;, \u0026quot;header\u0026quot; and \u0026quot;data\u0026quot; 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.\r\n\r\nThe functions PEM_read_bio() and PEM_read() are simple wrappers around\nPEM_read_bio_ex() and therefore these functions are also directly affected.\r\n\r\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.\r\n\r\nThe OpenSSL asn1parse command line application is also impacted by this issue.\r\n\r\n\n(CVE-2022-4450)","status":"published","published":"2024-11-01T11:07:47Z","modified":"2026-08-18T01:17:37.272294212Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"OESA-2024-2313","title":"openresty-openssl111 security update","description":"Security Fix(es):\r\n\r\nThe function PEM_read_bio_ex() reads a PEM file from a BIO and parses and\ndecodes the \u0026quot;name\u0026quot; (e.g. \u0026quot;CERTIFICATE\u0026quot;), any header data and the payload data.\nIf the function succeeds then the \u0026quot;name_out\u0026quot;, \u0026quot;header\u0026quot; and \u0026quot;data\u0026quot; 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.\r\n\r\nThe functions PEM_read_bio() and PEM_read() are simple wrappers around\nPEM_read_bio_ex() and therefore these functions are also directly affected.\r\n\r\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.\r\n\r\nThe OpenSSL asn1parse command line application is also impacted by this issue.\r\n\r\n\n(CVE-2022-4450)","status":"published","published":"2024-11-01T11:07:47Z","modified":"2026-08-18T01:17:36.000618992Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:41.595342Z"},{"id":"RHSA-2023:0946","title":"Red Hat Security Advisory: openssl security and bug fix update","status":"published","published":"2024-09-16T09:53:19Z","modified":"2026-10-15T10:03:41Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:10.611604Z"},{"id":"RHSA-2023:1199","title":"Red Hat Security Advisory: openssl security and bug fix update","status":"published","published":"2024-09-16T09:53:29Z","modified":"2026-10-15T10:03:45Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:10.611604Z"},{"id":"RHSA-2023:1405","title":"Red Hat Security Advisory: openssl security update","status":"published","published":"2024-09-14T00:03:12Z","modified":"2026-10-15T10:03:48Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:10.611604Z"},{"id":"RHSA-2023:2165","title":"Red Hat Security Advisory: edk2 security, bug fix, and enhancement update","status":"published","published":"2024-09-16T09:06:15Z","modified":"2026-10-15T10:03:55Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:10.611604Z"},{"id":"RHSA-2023:2932","title":"Red Hat Security Advisory: edk2 security update","status":"published","published":"2025-08-04T10:26:50Z","modified":"2026-10-15T10:04:09Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:11.154197Z"},{"id":"RHSA-2023:3354","title":"Red Hat Security Advisory: Red Hat JBoss Core Services Apache HTTP Server 2.4.51 SP2 security update","status":"published","published":"2024-09-14T00:03:54Z","modified":"2026-10-15T10:04:16Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:53:11.154197Z"},{"id":"RHSA-2023:3408","title":"Red Hat Security Advisory: openssl security update","status":"published","published":"2024-09-13T21:12:23Z","modified":"2026-10-15T10:04:18Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:11.154197Z"},{"id":"RHSA-2023:3420","title":"Red Hat Security Advisory: Red Hat JBoss Web Server 5.7.3 release and security update","status":"published","published":"2024-09-14T00:03:42Z","modified":"2026-10-15T10:04:19Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:11.154197Z"},{"id":"RLSA-2023:0946","title":"Important: openssl security and bug fix update","description":"OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.\n\nSecurity Fix(es):\n\n* openssl: X.400 address type confusion in X.509 GeneralName (CVE-2023-0286)\n\n* openssl: read buffer overflow in X.509 certificate verification (CVE-2022-4203)\n\n* openssl: timing attack in RSA Decryption implementation (CVE-2022-4304)\n\n* openssl: double free after calling PEM_read_bio_ex (CVE-2022-4450)\n\n* openssl: use-after-free following BIO_new_NDEF (CVE-2023-0215)\n\n* openssl: invalid pointer dereference in d2i_PKCS7 functions (CVE-2023-0216)\n\n* openssl: NULL dereference validating DSA public key (CVE-2023-0217)\n\n* openssl: NULL dereference during PKCS7 data verification (CVE-2023-0401)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n\nBug Fix(es):\n\n* HMAC generation should reject key lengths \u003c 112 bits or provide an indicator in FIPS mode (BZ#2144000)\n\n* In FIPS mode, openssl should set a minimum length for passwords in PBKDF2 (BZ#2144003)\n\n* stunnel consumes high amount of memory when pestered with TCP connections without a TLS handshake (BZ#2144008)\n\n* In FIPS mode, openssl should reject SHAKE as digest for RSA-OAEP or provide an indicator (BZ#2144010)\n\n* In FIPS mode, openssl should reject RSASSA-PSS salt lengths larger than the output size of the hash function used, or provide an indicator (BZ#2144012)\n\n* In FIPS mode, openssl should reject RSA signatures with X9.31 padding, or provide an indicator (BZ#2144015)\n\n* In FIPS mode, openssl should reject SHA-224, SHA-384, SHA-512-224, and SHA-512-256 as hashes for hash-based DRBGs, or provide an indicator after 2023-05-16 (BZ#2144017)\n\n* In FIPS mode, openssl should reject KDF input and output key lengths \u003c 112 bits or provide an indicator (BZ#2144019)\n\n* In FIPS mode, openssl should reject RSA keys \u003c 2048 bits when using EVP_PKEY_decapsulate, or provide an indicator (BZ#2145170)\n\n* Rocky Linux9.1 Nightly[0912] - error:03000093:digital envelope routines::command not supported when git clone is run with configured ibmca engine backed by libica.so.4 (OpenSSL 3.0) (BZ#2149010)\n\n* OpenSSL FIPS checksum code needs update (BZ#2158412)","status":"published","published":"2023-03-29T16:47:51.524711Z","modified":"2026-02-05T10:30:09.928457Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:24.322216Z"},{"id":"UBUNTU-CVE-2022-4450","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. 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.","status":"published","published":"2023-02-07T00:00:00Z","modified":"2026-10-05T19:20:11.886217817Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T16:53:56.473586Z"},{"id":"ALSA-2023:0946","title":"Moderate: openssl security and bug fix update","description":"OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.\n\nSecurity Fix(es):\n\n* openssl: read buffer overflow in X.509 certificate verification (CVE-2022-4203)\n* openssl: timing attack in RSA Decryption implementation (CVE-2022-4304)\n* openssl: double free after calling PEM_read_bio_ex (CVE-2022-4450)\n* openssl: use-after-free following BIO_new_NDEF (CVE-2023-0215)\n* openssl: invalid pointer dereference in d2i_PKCS7 functions (CVE-2023-0216)\n* openssl: NULL dereference validating DSA public key (CVE-2023-0217)\n* openssl: X.400 address type confusion in X.509 GeneralName (CVE-2023-0286)\n* openssl: NULL dereference during PKCS7 data verification (CVE-2023-0401)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n\nBug Fix(es):\n\n* HMAC generation should reject key lengths \u003c 112 bits or provide an indicator in FIPS mode (BZ#2144000)\n* In FIPS mode, openssl should set a minimum length for passwords in PBKDF2 (BZ#2144003)\n* stunnel consumes high amount of memory when pestered with TCP connections without a TLS handshake (BZ#2144008)\n* In FIPS mode, openssl should reject SHAKE as digest for RSA-OAEP or provide an indicator (BZ#2144010)\n* In FIPS mode, openssl should reject RSASSA-PSS salt lengths larger than the output size of the hash function used, or provide an indicator (BZ#2144012)\n* In FIPS mode, openssl should reject RSA signatures with X9.31 padding, or provide an indicator (BZ#2144015)\n* In FIPS mode, openssl should reject SHA-224, SHA-384, SHA-512-224, and SHA-512-256 as hashes for hash-based DRBGs, or provide an indicator after 2023-05-16 (BZ#2144017)\n* In FIPS mode, openssl should reject KDF input and output key lengths \u003c 112 bits or provide an indicator (BZ#2144019)\n* In FIPS mode, openssl should reject RSA keys \u003c 2048 bits when using EVP_PKEY_decapsulate, or provide an indicator (BZ#2145170)\n* AlmaLinux9.1 Nightly[0912] - error:03000093:digital envelope routines::command not supported when git clone is run with configured ibmca engine backed by libica.so.4 (OpenSSL 3.0) (BZ#2149010)\n* OpenSSL FIPS checksum code needs update (BZ#2158412)","status":"published","published":"2023-02-28T00:00:00Z","modified":"2026-10-29T11:31:23.783726741Z","updated_at":"2026-11-02T15:27:51.655726Z"},{"id":"ALSA-2023:1405","title":"Important: openssl security update","description":"OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.\n\nSecurity Fix(es):\n\n* openssl: X.400 address type confusion in X.509 GeneralName (CVE-2023-0286)\n* openssl: timing attack in RSA Decryption implementation (CVE-2022-4304)\n* openssl: double free after calling PEM_read_bio_ex (CVE-2022-4450)\n* openssl: use-after-free following BIO_new_NDEF (CVE-2023-0215)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2023-03-22T00:00:00Z","modified":"2026-10-29T11:02:03.643225173Z","updated_at":"2026-11-02T15:27:51.655726Z"},{"id":"ALSA-2023:2165","title":"Important: edk2 security, bug fix, and enhancement update","description":"EDK (Embedded Development Kit) is a project to enable UEFI support for Virtual Machines. This package contains a sample 64-bit UEFI firmware for QEMU and KVM. \n\nSecurity Fix(es):\n\n* openssl: X.400 address type confusion in X.509 GeneralName (CVE-2023-0286)\n* edk2: integer underflow in SmmEntryPoint function leads to potential SMM privilege escalation (CVE-2021-38578)\n* openssl: timing attack in RSA Decryption implementation (CVE-2022-4304)\n* openssl: double free after calling PEM_read_bio_ex (CVE-2022-4450)\n* openssl: use-after-free following BIO_new_NDEF (CVE-2023-0215)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n\nAdditional Changes:\n\nFor detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.","status":"published","published":"2023-05-09T00:00:00Z","modified":"2026-10-29T11:30:52.693252589Z","updated_at":"2026-11-02T15:27:51.655726Z"},{"id":"ALSA-2023:2932","title":"Important: edk2 security update","description":"EDK (Embedded Development Kit) is a project to enable UEFI support for Virtual Machines. This package contains a sample 64-bit UEFI firmware for QEMU and KVM. \n\nSecurity Fix(es):\n\n* openssl: X.400 address type confusion in X.509 GeneralName (CVE-2023-0286)\n* openssl: timing attack in RSA Decryption implementation (CVE-2022-4304)\n* openssl: double free after calling PEM_read_bio_ex (CVE-2022-4450)\n* openssl: use-after-free following BIO_new_NDEF (CVE-2023-0215)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n\nAdditional Changes:\n\nFor detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.","status":"published","published":"2023-05-16T00:00:00Z","modified":"2026-10-29T11:02:05.500451926Z","updated_at":"2026-11-02T15:27:52.091404Z"},{"id":"CLSA-2023-1680206329","title":"openssl: Fix of 2 CVEs","description":"- CVE-2022-4304: fix timing based side channel in RSA decryption\n- CVE-2022-4450: avoid dangling pointers in PEM_read_bio_ex()","status":"published","published":"2023-03-30T19:58:49Z","modified":"2026-06-01T00:33:20.321970233Z","updated_at":"2026-11-02T15:43:40.176048Z"},{"id":"CLSA-2023-1680210075","title":"openssl: Fix of 2 CVEs","description":"- CVE-2022-4304: fix timing based side channel in RSA decryption\n- CVE-2022-4450: avoid dangling pointers in PEM_read_bio_ex()","status":"published","published":"2023-03-30T21:01:15Z","modified":"2026-06-01T00:33:21.823404666Z","updated_at":"2026-11-02T15:43:40.176048Z"},{"id":"DEBIAN-CVE-2022-4450","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.  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.","status":"published","published":"2023-02-08T20:15:23.973Z","modified":"2026-11-03T06:02:59.78892135Z","updated_at":"2026-11-03T06:43:01.507088Z"},{"id":"DLA-3325-1","title":"openssl - security update","status":"published","published":"2023-02-20T00:00:00Z","modified":"2026-03-09T01:19:40.983935Z","updated_at":"2026-11-02T15:46:11.734021Z"},{"id":"DSA-5343-1","title":"openssl - security update","status":"published","published":"2023-02-07T00:00:00Z","modified":"2026-03-09T02:09:47.149297Z","updated_at":"2026-11-02T15:46:17.543497Z"},{"id":"MGASA-2023-0130","title":"Updated openssl packages fix security vulnerability","description":"A read buffer overrun can be triggered in X.509 certificate verification,\nspecifically in name constraint checking. Note that this occurs after\ncertificate chain signature verification and requires either a CA to have\nsigned the malicious certificate or for the application to continue\ncertificate verification despite failure to construct a path to a trusted\nissuer. The read buffer overrun might result in a crash which could lead\nto a denial of service attack. In theory it could also result in the\ndisclosure of private memory contents (such as private keys, or sensitive\nplaintext) although we are not aware of any working exploit leading to\nmemory contents disclosure as of the time of release of this advisory. In\na TLS client, this can be triggered by connecting to a malicious server.\nIn a TLS server, this can be triggered if the server requests client\nauthentication and a malicious client connects. (CVE-2022-4203)\n\nA timing based side channel exists in the OpenSSL RSA Decryption\nimplementation which could be sufficient to recover a plaintext across a\nnetwork in a Bleichenbacher style attack. To achieve a successful\ndecryption an attacker would have to be able to send a very large number\nof trial messages for decryption. The vulnerability affects all RSA\npadding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS\nconnection, RSA is commonly used by a client to send an encrypted\npre-master secret to the server. An attacker that had observed a genuine\nconnection between a client and a server could use this flaw to send trial\nmessages to the server and record the time taken to process them. After a\nsufficiently large number of messages the attacker could recover the\npre-master secret used for the original connection and thus be able to\ndecrypt the application data sent over that connection. (CVE-2022-4304)\n\nThe 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\ndata. If the function succeeds then the \"name_out\", \"header\" and \"data\"\narguments are populated with pointers to buffers containing the relevant\ndecoded data. The caller is responsible for freeing those buffers. It is\npossible to construct a PEM file that results in 0 bytes of payload data.\nIn this case PEM_read_bio_ex() will return a failure code but will\npopulate the header argument with a pointer to a buffer that has already\nbeen freed. If the caller also frees this buffer then a double free will\noccur. This will most likely lead to a crash. This could be exploited by\nan attacker who has the ability to supply malicious PEM files for parsing\nto achieve a denial of service attack. The functions PEM_read_bio() and\nPEM_read() are simple wrappers around PEM_read_bio_ex() and therefore\nthese functions are also directly affected. These functions are also\ncalled indirectly by a number of other OpenSSL functions including\nPEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are\nalso vulnerable. Some OpenSSL internal uses of these functions are not\nvulnerable because the caller does not free the header argument if\nPEM_read_bio_ex() returns a failure code. These locations include the\nPEM_read_bio_TYPE() functions as well as the decoders introduced in\nOpenSSL 3.0. The OpenSSL asn1parse command line application is also\nimpacted by this issue. (CVE-2022-4450)\n\nThe public API function BIO_new_NDEF is a helper function used for\nstreaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL\nto support the SMIME, CMS and PKCS7 streaming capabilities, but may also\nbe called directly by end user applications. The function receives a BIO\nfrom the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it\nto form a BIO chain, and then returns the new head of the BIO chain to the\ncaller. Under certain conditions, for example if a CMS recipient public\nkey is invalid, the new filter BIO is freed and the function returns a\nNULL result indicating a failure. However, in this case, the BIO chain is\nnot properly cleaned up and the BIO passed by the caller still retains\ninternal pointers to the previously freed filter BIO. If the caller then\ngoes on to call BIO_pop() on the BIO then a use-after-free will occur.\nThis will most likely result in a crash. This scenario occurs directly in\nthe internal function B64_write_ASN1() which may cause BIO_new_NDEF() to\nbe called and will subsequently call BIO_pop() on the BIO. This internal\nfunction is in turn called by the public API functions\nPEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream,\nPEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and\nSMIME_write_PKCS7. Other public API functions that may be impacted by this\ninclude i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7,\ni2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL cms and smime\ncommand line applications are similarly affected. (CVE-2023-0215)\n\nAn invalid pointer dereference on read can be triggered when an\napplication tries to load malformed PKCS7 data with the d2i_PKCS7(),\nd2i_PKCS7_bio() or d2i_PKCS7_fp() functions. The result of the dereference\nis an application crash which could lead to a denial of service attack.\nThe TLS implementation in OpenSSL does not call this function however\nthird party applications might call these functions on untrusted data.\n(CVE-2023-0216)\n\nAn invalid pointer dereference on read can be triggered when an\napplication tries to check a malformed DSA public key by the\nEVP_PKEY_public_check() function. This will most likely lead to an\napplication crash. This function can be called on public keys supplied\nfrom untrusted sources which could allow an attacker to cause a denial of\nservice attack. The TLS implementation in OpenSSL does not call this\nfunction but applications might call the function if there are additional\nsecurity requirements imposed by standards such as FIPS 140-3.\n(CVE-2023-0217)\n\nThere is a type confusion vulnerability relating to X.400 address\nprocessing inside an X.509 GeneralName. X.400 addresses were parsed as an\nASN1_STRING but the public structure definition for GENERAL_NAME\nincorrectly specified the type of the x400Address field as ASN1_TYPE. This\nfield is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp\nas an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled\n(i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this\nvulnerability may allow an attacker to pass arbitrary pointers to a memcmp\ncall, enabling them to read memory contents or enact a denial of service.\nIn most cases, the attack requires the attacker to provide both the\ncertificate chain and CRL, neither of which need to have a valid\nsignature. If the attacker only controls one of these inputs, the other\ninput must already contain an X.400 address as a CRL distribution point,\nwhich is uncommon. As such, this vulnerability is most likely to only\naffect applications which have implemented their own functionality for\nretrieving CRLs over a network. (CVE-2023-0286)\n\nA NULL pointer can be dereferenced when signatures are being verified on\nPKCS7 signed or signedAndEnveloped data. In case the hash algorithm used\nfor the signature is known to the OpenSSL library but the implementation\nof the hash algorithm is not available the digest initialization will\nfail. There is a missing check for the return value from the\ninitialization function which later leads to invalid usage of the digest\nAPI most likely leading to a crash. The unavailability of an algorithm can\nbe caused by using FIPS enabled configuration of providers or more\ncommonly by not loading the legacy provider. PKCS7 data is processed by\nthe SMIME library calls and also by the time stamp (TS) library calls. The\nTLS implementation in OpenSSL does not call these functions however third\nparty applications would be affected if they call these functions to\nverify signatures on untrusted data. (CVE-2023-0401)\n\nA security vulnerability has been identified in all supported versions of\nOpenSSL related to the verification of X.509 certificate chains that\ninclude policy constraints. Attackers may be able to exploit this\nvulnerability by creating a malicious certificate chain that triggers\nexponential use of computational resources, leading to a denial-of-service\n(DoS) attack on affected systems. Policy processing is disabled by default\nbut can be enabled by passing the `-policy' argument to the command line\nutilities or by calling the `X509_VERIFY_PARAM_set1_policies()' function.\n(CVE-2023-0464)\n\nApplications that use a non-default option when verifying certificates may\nbe vulnerable to an attack from a malicious CA to circumvent certain\nchecks. Invalid certificate policies in leaf certificates are silently\nignored by OpenSSL and other certificate policy checks are skipped for\nthat certificate. A malicious CA could use this to deliberately assert\ninvalid certificate policies in order to circumvent policy checking on the\ncertificate altogether. Policy processing is disabled by default but can\nbe enabled by passing the `-policy' argument to the command line utilities\nor by calling the `X509_VERIFY_PARAM_set1_policies()' function. (CVE-2023-0465)\n\nThe function X509_VERIFY_PARAM_add0_policy() is documented to implicitly\nenable the certificate policy check when doing certificate verification.\nHowever the implementation of the function does not enable the check which\nallows certificates with invalid or incorrect policies to pass the\ncertificate verification. As suddenly enabling the policy check could\nbreak existing deployments it was decided to keep the existing behavior of\nthe X509_VERIFY_PARAM_add0_policy() function. Instead the applications\nthat require OpenSSL to perform certificate policy check need to use\nX509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by\ncalling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK\nflag argument. Certificate policy checks are disabled by default in\nOpenSSL and are not commonly used by applications. (CVE-2023-0466)\n","status":"published","published":"2023-04-11T19:02:20Z","modified":"2026-04-16T04:40:45.664071043Z","updated_at":"2026-11-02T15:49:42.263076Z"},{"id":"openSUSE-SU-2024:12688-1","title":"libopenssl-1_1-devel-1.1.1t-1.1 on GA media","description":"These are all security issues fixed in the libopenssl-1_1-devel-1.1.1t-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T04:04:12.262678Z","updated_at":"2026-11-02T16:58:35.751245Z"},{"id":"openSUSE-SU-2024:12716-1","title":"libopenssl-3-devel-3.0.8-1.1 on GA media","description":"These are all security issues fixed in the libopenssl-3-devel-3.0.8-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T03:45:10.17388Z","updated_at":"2026-11-02T16:58:35.751245Z"},{"id":"RLSA-2023:1405","title":"Important: openssl security update","description":"OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.\n\nSecurity Fix(es):\n\n* openssl: X.400 address type confusion in X.509 GeneralName (CVE-2023-0286)\n\n* openssl: timing attack in RSA Decryption implementation (CVE-2022-4304)\n\n* openssl: double free after calling PEM_read_bio_ex (CVE-2022-4450)\n\n* openssl: use-after-free following BIO_new_NDEF (CVE-2023-0215)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2023-03-28T13:07:30.491037Z","modified":"2026-02-05T08:15:11.888694Z","updated_at":"2026-11-02T15:53:24.322216Z"},{"id":"RUSTSEC-2023-0010","title":"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\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\n`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\nfunctions including `PEM_X509_INFO_read_bio_ex()` and\n`SSL_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.","status":"published","published":"2023-02-07T12:00:00Z","modified":"2023-11-08T04:10:48.273182Z","updated_at":"2026-11-02T15:53:39.971022Z"},{"id":"SUSE-SU-2023:0309-1","title":"Security update for openssl-1_1","description":"This update for openssl-1_1 fixes the following issues:\n\n- CVE-2023-0286: Fixed X.400 address type confusion in X.509 GENERAL_NAME_cmp for x400Address (bsc#1207533).\n- CVE-2023-0215: Fixed use-after-free following BIO_new_NDEF() (bsc#1207536).\n- CVE-2022-4450: Fixed double free after calling PEM_read_bio_ex() (bsc#1207538).\n- CVE-2022-4304: Fixed timing Oracle in RSA Decryption (bsc#1207534).\n","status":"published","published":"2023-02-07T16:34:19Z","modified":"2026-02-04T04:00:18.422715Z","updated_at":"2026-11-02T15:53:51.853735Z"},{"id":"SUSE-SU-2023:0310-1","title":"Security update for openssl-1_1","description":"This update for openssl-1_1 fixes the following issues:\n\n- CVE-2023-0286: Fixed X.400 address type confusion in X.509 GENERAL_NAME_cmp for x400Address (bsc#1207533).\n- CVE-2023-0215: Fixed use-after-free following BIO_new_NDEF() (bsc#1207536).\n- CVE-2022-4450: Fixed double free after calling PEM_read_bio_ex() (bsc#1207538).\n- CVE-2022-4304: Fixed timing Oracle in RSA Decryption (bsc#1207534).\n- FIPS: list only FIPS approved public key algorithms (bsc#1121365, bsc#1198472)\n","status":"published","published":"2023-02-07T16:35:44Z","modified":"2026-02-04T03:50:56.363395Z","updated_at":"2026-11-02T15:53:51.853735Z"},{"id":"SUSE-SU-2023:0311-1","title":"Security update for openssl-1_1","description":"This update for openssl-1_1 fixes the following issues:\n\n- CVE-2023-0286: Fixed X.400 address type confusion in X.509 GENERAL_NAME_cmp for x400Address (bsc#1207533).\n- CVE-2023-0215: Fixed use-after-free following BIO_new_NDEF() (bsc#1207536).\n- CVE-2022-4450: Fixed double free after calling PEM_read_bio_ex() (bsc#1207538).\n- CVE-2022-4304: Fixed timing Oracle in RSA Decryption (bsc#1207534).\n","status":"published","published":"2023-02-07T16:36:43Z","modified":"2026-02-04T03:29:21.711014Z","updated_at":"2026-11-02T15:53:51.853735Z"},{"id":"SUSE-SU-2023:0312-1","title":"Security update for openssl-3","description":"This update for openssl-3 fixes the following issues:\n\nSecurity fixes:\n\n- CVE-2023-0286: Fixed X.400 address type confusion in X.509 GENERAL_NAME_cmp for x400Address (bsc#1207533).\n- CVE-2023-0401: Fixed NULL pointer dereference during PKCS7 data verification (bsc#1207541).\n- CVE-2023-0217: Fixed NULL pointer dereference validating DSA public key (bsc#1207540).\n- CVE-2023-0216: Fixed invalid pointer dereference in d2i_PKCS7 functions (bsc#1207539).\n- CVE-2023-0215: Fixed use-after-free following BIO_new_NDEF() (bsc#1207536).\n- CVE-2022-4450: Fixed double free after calling PEM_read_bio_ex() (bsc#1207538).\n- CVE-2022-4304: Fixed timing Oracle in RSA Decryption (bsc#1207534).\n- CVE-2022-4203: Fixed read Buffer Overflow with X.509 Name Constraints (bsc#1207535).\n\nNon-security fixes:\n\n- Fix SHA, SHAKE, KECCAK ASM and EC ASM flag passing (bsc#1206222).\n- Enable zlib compression support (bsc#1195149).\n- Add crypto-policies dependency.\n","status":"published","published":"2023-02-07T16:54:57Z","modified":"2026-02-04T03:56:54.34776Z","updated_at":"2026-11-02T15:53:51.853735Z"},{"id":"USN-5844-1","title":"openssl vulnerabilities","description":"David Benjamin discovered that OpenSSL incorrectly handled X.400 address\nprocessing. A remote attacker could possibly use this issue to read\narbitrary memory contents or cause OpenSSL to crash, resulting in a denial\nof service. (CVE-2023-0286)\n\nCorey Bonnell discovered that OpenSSL incorrectly handled X.509 certificate\nverification. A remote attacker could possibly use this issue to cause\nOpenSSL to crash, resulting in a denial of service. This issue only\naffected Ubuntu 22.04 LTS and Ubuntu 22.10. (CVE-2022-4203)\n\nHubert Kario discovered that OpenSSL had a timing based side channel in the\nOpenSSL RSA Decryption implementation. A remote attacker could possibly use\nthis issue to recover sensitive information. (CVE-2022-4304)\n\nDawei Wang discovered that OpenSSL incorrectly handled parsing certain PEM\ndata. A remote attacker could possibly use this issue to cause OpenSSL to\ncrash, resulting in a denial of service. (CVE-2022-4450)\n\nOctavio Galland and Marcel Böhme discovered that OpenSSL incorrectly\nhandled streaming ASN.1 data. A remote attacker could use this issue to\ncause OpenSSL to crash, resulting in a denial of service, or possibly\nexecute arbitrary code. (CVE-2023-0215)\n\nMarc Schönefeld discovered that OpenSSL incorrectly handled malformed PKCS7\ndata. A remote attacker could possibly use this issue to cause OpenSSL to\ncrash, resulting in a denial of service. This issue only affected Ubuntu\n22.04 LTS and Ubuntu 22.10. (CVE-2023-0216)\n\nKurt Roeckx discovered that OpenSSL incorrectly handled validating certain\nDSA public keys. A remote attacker could possibly use this issue to cause\nOpenSSL to crash, resulting in a denial of service. This issue only\naffected Ubuntu 22.04 LTS and Ubuntu 22.10. (CVE-2023-0217)\n\nHubert Kario and Dmitry Belyavsky discovered that OpenSSL incorrectly\nvalidated certain signatures. A remote attacker could possibly use this\nissue to cause OpenSSL to crash, resulting in a denial of service. This\nissue only affected Ubuntu 22.04 LTS and Ubuntu 22.10. (CVE-2023-0401)\n","status":"published","published":"2023-02-07T17:20:39Z","modified":"2026-04-27T16:47:20.687515601Z","updated_at":"2026-11-02T16:58:16.738762Z"},{"id":"USN-6564-1","title":"nodejs vulnerabilities","description":"Hubert Kario discovered that Node.js incorrectly handled certain inputs. If a\nuser or an automated system were tricked into opening a specially crafted input\nfile, a remote attacker could possibly use this issue to obtain sensitive\ninformation. (CVE-2022-4304)\n\nCarpetFuzz, Dawei Wang discovered that Node.js incorrectly handled certain\ninputs. If a user or an automated system were tricked into opening a specially\ncrafted input file, a remote attacker could possibly use this issue to cause a\ndenial of service. (CVE-2022-4450)\n\nOctavio Galland and Marcel Böhme discovered that Node.js incorrectly handled\ncertain inputs. If a user or an automated system were tricked into opening a\nspecially crafted input file, a remote attacker could possibly use this issue\nto cause a denial of service. (CVE-2023-0215)\n\nDavid Benjamin discovered that Node.js incorrectly handled certain inputs. If a\nuser or an automated system were tricked into opening a specially crafted input\nfile, a remote attacker could possibly use this issue to obtain sensitive\ninformation. (CVE-2023-0286)\n\nHubert Kario and Dmitry Belyavsky discovered that Node.js incorrectly handled\ncertain inputs. If a user or an automated system were tricked into opening a\nspecially crafted input file, a remote attacker could possibly use this issue\nto cause a denial of service. (CVE-2023-0401)\n","status":"published","published":"2024-01-03T09:31:07Z","modified":"2026-04-27T17:17:25.476185618Z","updated_at":"2026-11-02T16:58:17.305935Z"},{"id":"USN-7894-1","title":"edk2 vulnerabilities","description":"It was discovered that EDK II was susceptible to a predictable TCP Initial\nSequence Number. An attacker could possibly use this issue to gain\nunauthorized access. This issue only affected Ubuntu 22.04 LTS, and Ubuntu\n24.04 LTS. (CVE-2023-45236, CVE-2023-45237)\n\nIt was discovered that EDK II incorrectly handled S3 sleep. An attacker\ncould possibly use this issue to cause a denial of service. This issue only\naffected Ubuntu 22.04 LTS, and Ubuntu 24.04 LTS. (CVE-2024-1298)\n\nIt was discovered that the EDK II PE/COFF loader incorrectly handled\ncertain memory operations. An attacker could possibly use this issue to\ncause a denial of service, obtain sensitive information, or execute\narbitrary code. This issue only affected Ubuntu 22.04 LTS, and Ubuntu\n24.04 LTS. (CVE-2024-38796)\n\nIt was discovered that the EDK II PE image hashing function incorrectly\nhandled certain memory operations. An attacker could possibly use this\nissue to cause a denial of service, or execute arbitrary code.\n(CVE-2024-38797)\n\nIt was discovered that the EDK II BIOS incorrectly handled certain memory\noperations. An attacker could possibly use this issue to cause a denial of\nservice. (CVE-2024-38805, CVE-2025-2295)\n\nIt was discovered that EDK II incorrectly handled the enabling of MCE. An\nattacker could possibly use this issue to cause a denial of service, or\nexecute arbitrary code. (CVE-2025-3770)\n\nIt was discovered that the OpenSSL library embedded in EDK II contained\nmultiple vulnerabilties. An attacker could possibly use these issues to\ncause a denial of service, obtain sensitive information, or execute\narbitrary code. (CVE-2021-3712, CVE-2022-0778, CVE-2022-4304,\nCVE-2022-4450, CVE-2023-0215, CVE-2023-0286, CVE-2023-0464, CVE-2023-0465,\nCVE-2023-0466, CVE-2023-2650, CVE-2023-3446, CVE-2023-3817, CVE-2023-5678,\nCVE-2023-6237, CVE-2024-0727, CVE-2024-13176, CVE-2024-2511,\nCVE-2024-41996, CVE-2024-4741, CVE-2024-5535, CVE-2024-6119, CVE-2024-9143,\nCVE-2025-9232)","status":"published","published":"2025-11-26T15:05:43Z","modified":"2026-11-09T12:46:35.954753636Z","updated_at":"2026-11-09T12:55:09.79476Z"}]}}