{"id":"CVE-2022-4203","aliases":["ALPINE-CVE-2022-4203","ALSA-2023:0946","BELL-CVE-2022-4203","DEBIAN-CVE-2022-4203","EUVD-2023-0809","GHSA-w67w-mw4j-8qrv","MGASA-2023-0130","RHSA-2023:0946","RHSA-2023:1199","RLSA-2023:0946","RUSTSEC-2023-0008","SUSE-SU-2023:0312-1","UBUNTU-CVE-2022-4203","USN-5844-1","openSUSE-SU-2024:12716-1"],"status":"published","title":"X.509 Name Constraints Read Buffer Overflow","description":"A read buffer overrun can be triggered in X.509 certificate verification,\nspecifically in name constraint checking. Note that this occurs\nafter certificate chain signature verification and requires either a\nCA to have signed the malicious certificate or for the application to\ncontinue certificate verification despite failure to construct a path\nto a trusted issuer.\n\nThe read buffer overrun might result in a crash which could lead to\na denial of service attack. In theory it could also result in the disclosure\nof private memory contents (such as private keys, or sensitive plaintext)\nalthough we are not aware of any working exploit leading to memory\ncontents disclosure as of the time of release of this advisory.\n\nIn a TLS client, this can be triggered by connecting to a malicious\nserver. In a TLS server, this can be triggered if the server requests\nclient authentication and a malicious client connects.","severity":{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-11","score":0.01386,"percentile":0.72595,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-125"],"published":"2023-02-07T00:00:00Z","modified":"2026-11-03T08:04:11Z","fixes":[{"ecosystem":"crates.io","package":"openssl-src","fixed_in":["300.0.12"],"sources":["ghsa","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.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":"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":"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":"300.0.0"},{"fixed":"300.0.12"}]}]},{"source":"osv","ecosystem":"Alpine:v3.17","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.19","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.20","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.8-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":"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":"crates.io","package":"openssl-src","ranges":[{"type":"SEMVER","events":[{"introduced":"300.0.0"},{"fixed":"300.0.12"}]}]},{"source":"osv","ecosystem":"Mageia:8","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1t-1.mga8"}]}],"bundled":11},{"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":"Rocky Linux:9","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.1-47.el9_1"}]}],"bundled":8},{"source":"osv","ecosystem":"crates.io","package":"openssl-src","ranges":[{"type":"SEMVER","events":[{"introduced":"300.0.0"},{"fixed":"300.0.12"}]}]},{"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: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":"openSUSE:Tumbleweed","package":"openssl-3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.8-1.1"}]}],"bundled":8}],"products":[{"vendor":"openssl","product":"openssl"}],"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=c927a3492698c254637da836762f9b1f86cffabc","tags":["patch","x_transferred","Mailing List","Patch","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://nvd.nist.gov/vuln/detail/CVE-2022-4203","tags":["advisory"]},{"url":"https://rustsec.org/advisories/RUSTSEC-2023-0008.html","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-w67w-mw4j-8qrv"},{"url":"https://security.alpinelinux.org/vuln/CVE-2022-4203","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://docs.bell-sw.com/security/cves/CVE-2022-4203","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/4xxx/CVE-2022-4203.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2022-4203","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://access.redhat.com/errata/RHSA-2023:1405","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://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","report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-4304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-4304","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-4450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-4450","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-0215","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/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://nvd.nist.gov/vuln/detail/CVE-2023-0286","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-0401","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/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://errata.rockylinux.org/RLSA-2023:0946","tags":["advisory"]},{"url":"https://crates.io/crates/openssl-src","tags":["package"]},{"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/1207533","tags":["report"]},{"url":"https://bugzilla.suse.com/1207534","tags":["report"]},{"url":"https://bugzilla.suse.com/1207535","tags":["report"]},{"url":"https://bugzilla.suse.com/1207536","tags":["report"]},{"url":"https://bugzilla.suse.com/1207538","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-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-0216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-0217","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-0286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-0401","tags":["web"]},{"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-2022-4450","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":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2022-4203","title":"X.509 Name Constraints Read Buffer Overflow","description":"A read buffer overrun can be triggered in X.509 certificate verification,\nspecifically in name constraint checking. Note that this occurs\nafter certificate chain signature verification and requires either a\nCA to have signed the malicious certificate or for the application to\ncontinue certificate verification despite failure to construct a path\nto a trusted issuer.\n\nThe read buffer overrun might result in a crash which could lead to\na denial of service attack. In theory it could also result in the disclosure\nof private memory contents (such as private keys, or sensitive plaintext)\nalthough we are not aware of any working exploit leading to memory\ncontents disclosure as of the time of release of this advisory.\n\nIn a TLS client, this can be triggered by connecting to a malicious\nserver. In a TLS server, this can be triggered if the server requests\nclient authentication and a malicious client connects.","status":"published","published":"2023-02-24T14:53:08.485Z","modified":"2025-11-04T19:14:06.67Z","cvss":[{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"adp"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T14:34:37.932195Z"}],"euvd":[{"id":"EUVD-2023-0809","description":"A read buffer overrun can be triggered in X.509 certificate verification,\nspecifically in name constraint checking. Note that this occurs\nafter certificate chain signature verification and requires either a\nCA to have signed the malicious certificate or for the application to\ncontinue certificate verification despite failure to construct a path\nto a trusted issuer.\n\nThe read buffer overrun might result in a crash which could lead to\na denial of service attack. In theory it could also result in the disclosure\nof private memory contents (such as private keys, or sensitive plaintext)\nalthough we are not aware of any working exploit leading to memory\ncontents disclosure as of the time of release of this advisory.\n\nIn a TLS client, this can be triggered by connecting to a malicious\nserver. In a TLS server, this can be triggered if the server requests\nclient authentication and a malicious client connects.","status":"published","published":"2023-02-24T14:53:08Z","modified":"2025-11-04T19:14:06Z","cvss":[{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T19:49:23.324829Z"}],"ghsa":[{"id":"GHSA-w67w-mw4j-8qrv","title":"openssl-src contains Read Buffer Overflow in X.509 Name Constraint","description":"A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs\nafter certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to\ncontinue certificate verification despite failure to construct a path to a trusted issuer.\n\nThe read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory.\n\nIn a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.","status":"published","published":"2023-02-08T22:27:42Z","modified":"2025-11-04T22:09:13Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T14:39:06.376137Z"}],"nvd":[{"id":"CVE-2022-4203","description":"A read buffer overrun can be triggered in X.509 certificate verification,\nspecifically in name constraint checking. Note that this occurs\nafter certificate chain signature verification and requires either a\nCA to have signed the malicious certificate or for the application to\ncontinue certificate verification despite failure to construct a path\nto a trusted issuer.\n\nThe read buffer overrun might result in a crash which could lead to\na denial of service attack. In theory it could also result in the disclosure\nof private memory contents (such as private keys, or sensitive plaintext)\nalthough we are not aware of any working exploit leading to memory\ncontents disclosure as of the time of release of this advisory.\n\nIn a TLS client, this can be triggered by connecting to a malicious\nserver. In a TLS server, this can be triggered if the server requests\nclient authentication and a malicious client connects.","status":"published","published":"2023-02-24T15:15:11.98Z","modified":"2026-06-17T05:20:14.5Z","cvss":[{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"},{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"secondary"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T14:07:36.601381Z"}],"osv":[{"id":"ALPINE-CVE-2022-4203","description":"A read buffer overrun can be triggered in X.509 certificate verification,\nspecifically in name constraint checking. Note that this occurs\nafter certificate chain signature verification and requires either a\nCA to have signed the malicious certificate or for the application to\ncontinue certificate verification despite failure to construct a path\nto a trusted issuer.\n\nThe read buffer overrun might result in a crash which could lead to\na denial of service attack. In theory it could also result in the disclosure\nof private memory contents (such as private keys, or sensitive plaintext)\nalthough we are not aware of any working exploit leading to memory\ncontents disclosure as of the time of release of this advisory.\n\nIn a TLS client, this can be triggered by connecting to a malicious\nserver. In a TLS server, this can be triggered if the server requests\nclient authentication and a malicious client connects.","status":"published","published":"2023-02-24T15:15:11.98Z","modified":"2026-11-03T07:18:33.740297342Z","cvss":[{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-03T07:50:38.973973Z"},{"id":"BELL-CVE-2022-4203","title":"CVE-2022-4203 does not affect BellSoft software","status":"withdrawn","published":"2023-08-31T12:14:27.343517Z","modified":"2026-01-26T09:49:20.827977Z","cvss":[{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:17.151188Z"},{"id":"CVE-2022-4203","title":"X.509 Name Constraints Read Buffer Overflow","description":"A read buffer overrun can be triggered in X.509 certificate verification,\nspecifically in name constraint checking. Note that this occurs\nafter certificate chain signature verification and requires either a\nCA to have signed the malicious certificate or for the application to\ncontinue certificate verification despite failure to construct a path\nto a trusted issuer.\n\nThe read buffer overrun might result in a crash which could lead to\na denial of service attack. In theory it could also result in the disclosure\nof private memory contents (such as private keys, or sensitive plaintext)\nalthough we are not aware of any working exploit leading to memory\ncontents disclosure as of the time of release of this advisory.\n\nIn a TLS client, this can be triggered by connecting to a malicious\nserver. In a TLS server, this can be triggered if the server requests\nclient authentication and a malicious client connects.","status":"published","published":"2023-02-24T14:53:08.485Z","modified":"2026-11-11T10:30:49.177963297Z","cvss":[{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-11T11:06:22.593744Z"},{"id":"DEBIAN-CVE-2022-4203","description":"A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer.  The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory.  In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.","status":"published","published":"2023-02-24T15:15:11.98Z","modified":"2026-11-03T08:04:11.075336439Z","cvss":[{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-03T08:23:07.763774Z"},{"id":"GHSA-w67w-mw4j-8qrv","title":"openssl-src contains Read Buffer Overflow in X.509 Name Constraint","description":"A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs\nafter certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to\ncontinue certificate verification despite failure to construct a path to a trusted issuer.\n\nThe read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory.\n\nIn a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.","status":"published","published":"2023-02-08T22:27:42Z","modified":"2026-09-10T03:49:52.23723155Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T15:46:58.04805Z"},{"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":"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-4203","description":"A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.","status":"published","published":"2023-02-07T00:00:00Z","modified":"2026-04-22T13:28:53.110028Z","cvss":[{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium"},{"version":"3.1","score":4.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T16:53:55.502114Z"},{"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":"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: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":"RUSTSEC-2023-0008","title":"X.509 Name Constraints Read Buffer Overflow","description":"A read buffer overrun can be triggered in X.509 certificate verification,\nspecifically in name constraint checking. Note that this occurs\nafter certificate chain signature verification and requires either a\nCA to have signed the malicious certificate or for the application to\ncontinue certificate verification despite failure to construct a path\nto a trusted issuer.\n\nThe read buffer overrun might result in a crash which could lead to\na denial of service attack. In theory it could also result in the disclosure\nof private memory contents (such as private keys, or sensitive plaintext)\nalthough we are not aware of any working exploit leading to memory\ncontents disclosure as of the time of release of this advisory.\n\nIn a TLS client, this can be triggered by connecting to a malicious\nserver. In a TLS server, this can be triggered if the server requests\nclient authentication and a malicious client connects.","status":"published","published":"2023-02-07T12:00:00Z","modified":"2023-11-08T04:10:37.466308Z","updated_at":"2026-11-02T15:53:39.971022Z"},{"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"}]}}