{"id":"CVE-2022-3358","aliases":["ALPINE-CVE-2022-3358","ALSA-2023:2523","BELL-CVE-2022-3358","DEBIAN-CVE-2022-3358","EUVD-2022-7013","GHSA-4f63-89w9-3jjv","RHSA-2023:2523","RUSTSEC-2022-0059","SUSE-SU-2022:3843-1","UBUNTU-CVE-2022-3358","USN-5710-1","openSUSE-SU-2024:12475-1"],"status":"published","title":"Using a Custom Cipher with NID_undef may lead to NULL encryption","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-10","score":0.04044,"percentile":0.90709,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-476"],"published":"2022-10-11T12:00:00Z","modified":"2026-11-03T08:03:00Z","exploits":[{"source":"metasploit","id":"auxiliary/scanner/ssl/ssl_version","title":"SSL/TLS Version Detection","type":"auxiliary","date":"2014-10-14","verified":true,"url":"https://www.rapid7.com/db/modules/auxiliary/scanner/ssl/ssl_version"}],"fixes":[{"ecosystem":"crates.io","package":"openssl-src","fixed_in":["300.0.10"],"sources":["ghsa","osv"]},{"ecosystem":"Alpine:v3.17","package":"openssl","fixed_in":["3.0.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.18","package":"openssl","fixed_in":["3.0.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.19","package":"openssl","fixed_in":["3.0.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.20","package":"openssl","fixed_in":["3.0.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"openssl","fixed_in":["3.0.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"openssl","fixed_in":["3.0.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"openssl","fixed_in":["3.0.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"openssl","fixed_in":["3.0.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.15","package":"openssl3","fixed_in":["3.0.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.16","package":"openssl3","fixed_in":["3.0.6-r0"],"sources":["osv"]},{"ecosystem":"AlmaLinux:9","package":"openssl","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"AlmaLinux:9","package":"openssl-devel","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"AlmaLinux:9","package":"openssl-libs","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"AlmaLinux:9","package":"openssl-perl","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"openssl","fixed_in":["3.0.7-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"openssl","fixed_in":["3.0.7-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"openssl","fixed_in":["3.0.7-1"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-debuginfo","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-debugsource","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-devel","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-libs-debuginfo","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-perl","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl-debuginfo","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl-debugsource","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl-libs","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl-libs-debuginfo","fixed_in":["1:3.0.7-6.el9_2"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"openssl","fixed_in":["3.0.2-0ubuntu1.7"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"openssl-src","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"300.0.0"},{"fixed":"300.0.10"}]}]},{"source":"osv","ecosystem":"Alpine:v3.17","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.19","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.20","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.15","package":"openssl3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.16","package":"openssl3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.6-r0"}]}]},{"source":"osv","ecosystem":"AlmaLinux:9","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"AlmaLinux:9","package":"openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"AlmaLinux:9","package":"openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"AlmaLinux:9","package":"openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.7-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.7-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.7-1"}]}]},{"source":"osv","ecosystem":"crates.io","package":"openssl-src","ranges":[{"type":"SEMVER","events":[{"introduced":"300.0.0"},{"fixed":"300.0.10"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-libs-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"openssl-libs-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.0.7-6.el9_2"}]}]},{"source":"osv","ecosystem":"crates.io","package":"openssl-src","ranges":[{"type":"SEMVER","events":[{"introduced":"300.0.0"},{"fixed":"300.0.10"}]}]},{"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.11.1"}]}],"bundled":3},{"source":"osv","ecosystem":"openSUSE:Leap 15.4","package":"openssl-3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.1-150400.4.11.1"}]}],"bundled":3},{"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:22.04:LTS","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.2-0ubuntu1.7"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.2-0ubuntu1.7"}]}],"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"],"bundled":3},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"openssl-3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.7-1.1"}]}],"bundled":3}],"products":[{"vendor":"openssl","product":"openssl"}],"references":[{"url":"https://www.openssl.org/news/secadv/20221011.txt","tags":["x_transferred","Vendor Advisory","web","article","report"]},{"url":"https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=5485c56679d7c49b96e8fc8ca708b0b7e7c03c4b","tags":["x_transferred","web"]},{"url":"https://security.netapp.com/advisory/ntap-20221028-0014/","tags":["x_transferred","Third Party Advisory","advisory"]},{"url":"https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0023","tags":["x_transferred","Third Party Advisory","web"]},{"url":"https://security.gentoo.org/glsa/202402-08","tags":["vendor-advisory","x_transferred","advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3358","tags":["advisory"]},{"url":"https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=5485c56679d7c49b96e8fc8ca708b0b7e7c03c4b","tags":["web"]},{"url":"https://rustsec.org/advisories/RUSTSEC-2022-0059.html","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-4f63-89w9-3jjv"},{"url":"https://security.alpinelinux.org/vuln/CVE-2022-3358","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2023:2523","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2022-3358","tags":["report"]},{"url":"https://bugzilla.redhat.com/2134740","tags":["report"]},{"url":"https://errata.almalinux.org/9/ALSA-2023-2523.html","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2022-3358","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/3xxx/CVE-2022-3358.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2022-3358","tags":["advisory"]},{"url":"https://github.com/alexcrichton/openssl-src-rs","tags":["package"]},{"url":"https://security.netapp.com/advisory/ntap-20221028-0014","tags":["web"]},{"url":"https://access.redhat.com/security/updates/classification/#low","tags":["article"]},{"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=2060044","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2083879","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2094956","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2128412","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2129063","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2133809","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2134740","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2136250","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2137557","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2141597","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2141695","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2141748","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2142087","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2142121","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2142131","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2142517","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2144561","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2157965","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2168224","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2023/rhsa-2023_2523.json","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-3358","tags":["advisory","report"]},{"url":"https://crates.io/crates/openssl-src","tags":["package"]},{"url":"https://www.suse.com/support/update/announcement/2022/suse-su-20223843-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1204226","tags":["report"]},{"url":"https://bugzilla.suse.com/1204714","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3358","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3786","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2022-3358","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-5710-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2022-3602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-3786","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2022-3358","title":"Using a Custom Cipher with NID_undef may lead to NULL encryption","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","status":"published","published":"2022-10-11T15:00:14.123Z","modified":"2024-09-16T16:33:30.64Z","updated_at":"2026-11-02T14:34:33.24035Z"}],"euvd":[{"id":"EUVD-2022-7013","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","status":"published","published":"2022-10-11T15:00:14Z","modified":"2024-09-16T16:33:30Z","updated_at":"2026-11-03T00:55:50.59293Z"}],"ghsa":[{"id":"GHSA-4f63-89w9-3jjv","title":"Using a Custom Cipher with `NID_undef` may lead to NULL encryption","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","status":"published","published":"2022-10-11T19:00:29Z","modified":"2024-02-05T17:02:55Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"cwes":["CWE-476"],"updated_at":"2026-11-02T14:37:36.076201Z"}],"nvd":[{"id":"CVE-2022-3358","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","status":"published","published":"2022-10-11T15:15:10.233Z","modified":"2026-06-17T04:59:22.627Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high","assessor":"primary"}],"cwes":["CWE-476"],"updated_at":"2026-11-02T14:07:29.026521Z"}],"osv":[{"id":"ALPINE-CVE-2022-3358","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","status":"published","published":"2022-10-11T15:15:10.233Z","modified":"2026-11-03T07:18:33.454394821Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"updated_at":"2026-11-03T07:51:12.284675Z"},{"id":"BELL-CVE-2022-3358","title":"CVE-2022-3358 does not affect BellSoft software","status":"withdrawn","published":"2023-08-31T12:15:59.893311Z","modified":"2026-01-26T09:49:27.945287Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"updated_at":"2026-11-02T15:28:17.151188Z"},{"id":"DEBIAN-CVE-2022-3358","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","status":"published","published":"2022-10-11T15:15:10.233Z","modified":"2026-11-03T08:03:00.829422674Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"updated_at":"2026-11-03T08:24:39.643572Z"},{"id":"GHSA-4f63-89w9-3jjv","title":"Using a Custom Cipher with `NID_undef` may lead to NULL encryption","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","status":"published","published":"2022-10-11T19:00:29Z","modified":"2026-09-10T03:49:46.182272014Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"cwes":["CWE-476"],"updated_at":"2026-11-02T15:46:36.782754Z"},{"id":"RHSA-2023:2523","title":"Red Hat Security Advisory: openssl security and bug fix update","status":"published","published":"2024-09-16T09:52:48Z","modified":"2026-06-30T10:03:41Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:10.611604Z"},{"id":"UBUNTU-CVE-2022-3358","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","status":"published","published":"2022-10-11T15:15:00Z","modified":"2026-10-05T19:20:11.325988192Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"updated_at":"2026-11-02T16:53:54.697021Z"},{"id":"ALSA-2023:2523","title":"Low: 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: Using a Custom Cipher with NID_undef may lead to NULL encryption (CVE-2022-3358)\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:55.943545761Z","updated_at":"2026-11-02T15:27:51.655726Z"},{"id":"CVE-2022-3358","title":"Using a Custom Cipher with NID_undef may lead to NULL encryption","description":"OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).","status":"published","published":"2022-10-11T15:00:14.123Z","modified":"2026-11-11T10:30:51.780110895Z","updated_at":"2026-11-11T11:06:21.96633Z"},{"id":"openSUSE-SU-2024:12475-1","title":"libopenssl-3-devel-3.0.7-1.1 on GA media","description":"These are all security issues fixed in the libopenssl-3-devel-3.0.7-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T04:30:17.063132Z","updated_at":"2026-11-02T16:58:35.751245Z"},{"id":"RUSTSEC-2022-0059","title":"Using a Custom Cipher with `NID_undef` may lead to NULL encryption","description":"OpenSSL supports creating a custom cipher via the legacy `EVP_CIPHER_meth_new()`\nfunction and associated function calls. This function was deprecated in OpenSSL\n3.0 and application authors are instead encouraged to use the new provider\nmechanism in order to implement custom ciphers.\n\nOpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed\nto the `EVP_EncryptInit_ex2()`, `EVP_DecryptInit_ex2()` and `EVP_CipherInit_ex2()`\nfunctions (as well as other similarly named encryption and decryption\ninitialisation functions). Instead of using the custom cipher directly it\nincorrectly tries to fetch an equivalent cipher from the available providers.\nAn equivalent cipher is found based on the NID passed to `EVP_CIPHER_meth_new()`.\nThis NID is supposed to represent the unique NID for a given cipher. However it\nis possible for an application to incorrectly pass `NID_undef` as this value in\nthe call to `EVP_CIPHER_meth_new()`. When `NID_undef` is used in this way the\nOpenSSL encryption/decryption initialisation function will match the NULL cipher\nas being equivalent and will fetch this from the available providers. This will\nsucceed if the default provider has been loaded (or if a third party provider\nhas been loaded that offers this cipher). Using the NULL cipher means that the\nplaintext is emitted as the ciphertext.\n\nApplications are only affected by this issue if they call `EVP_CIPHER_meth_new()`\nusing `NID_undef` and subsequently use it in a call to an encryption/decryption\ninitialisation function. Applications that only use SSL/TLS are not impacted by\nthis issue.","status":"published","published":"2022-10-11T12:00:00Z","modified":"2023-11-08T04:09:40.031051Z","updated_at":"2026-11-02T15:53:39.971022Z"},{"id":"SUSE-SU-2022:3843-1","title":"Security update for openssl-3","description":"This update for openssl-3 fixes the following issues:\n\n- CVE-2022-3358: Fixed vulnerability where a custom cipher passed to EVP_CipherInit() could lead into NULL encryption being unexpectedly used (bsc#1204226).\n- CVE-2022-3602: Fixed a buffer overflow in the X.509 email address. (bsc#1204714)\n- CVE-2022-3786: Fixed another buffer overflow related to X.509 email address. (bsc#1204714)\n","status":"published","published":"2022-11-01T16:40:22Z","modified":"2026-02-04T04:10:49.982797Z","updated_at":"2026-11-02T15:53:51.440565Z"},{"id":"USN-5710-1","title":"openssl vulnerabilities","description":"It was discovered that OpenSSL incorrectly handled certain X.509 Email\nAddresses. If a certificate authority were tricked into signing a\nspecially-crafted certificate, a remote attacker could possibly use this\nissue to cause OpenSSL to crash, resulting in a denial of service. The\ndefault compiler options for affected releases reduce the vulnerability to\na denial of service. (CVE-2022-3602, CVE-2022-3786)\n\nIt was discovered that OpenSSL incorrectly handled applications creating\ncustom ciphers via the legacy EVP_CIPHER_meth_new() function. This issue\ncould cause certain applications that mishandled values to the function to\npossibly end up with a NULL cipher and messages in plaintext.\n(CVE-2022-3358)\n","status":"published","published":"2022-11-01T16:24:36Z","modified":"2026-04-27T16:32:25.316143292Z","updated_at":"2026-11-02T16:58:16.20937Z"}]}}