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 mechan…
Historical advisory saved 18 Nov 2026 03:29:42 UTC. The publisher may have updated it since then. Latest advisory.
euvd · EUVD-2022-7013
PublishedOpenSSL 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).
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Oct 11, 2022, 3:00:14 PM
dateUpdated: Sep 16, 2024, 4:33:30 PM
5 related source bulletins · separate from aliases
SUSE-SU-2022:3843-1: Security update for openssl-3
CVE-2022-3358 · CVE-2022-3602 · CVE-2022-3786
RHSA-2023:2523: Red Hat Security Advisory: openssl security and bug fix update
CVE-2022-3358
WID-SEC-W-2022-1690: OpenSSL: Schwachstelle ermöglicht Offenlegung von Informationen
CVE-2022-3358
openSUSE-SU-2024:12475-1: libopenssl-3-devel-3.0.7-1.1 on GA media
CVE-2022-3358 · CVE-2022-3602 · CVE-2022-3786
WID-SEC-W-2023-1542: Red Hat OpenShift: Mehrere Schwachstellen
CVE-2015-20107 · CVE-2018-25032 · CVE-2020-10735 · CVE-2020-16250 · CVE-2020-16251 · CVE-2020-17049 · CVE-2021-28861 · CVE-2021-3765 · CVE-2021-3807 · CVE-2021-4231 · CVE-2021-4235 · CVE-2021-4238 · CVE-2021-43519 · CVE-2021-43998 · CVE-2021-44531 · CVE-2021-44532 · CVE-2021-44533 · CVE-2021-44964 · CVE-2021-46828 · CVE-2021-46848 · CVE-2022-0670 · CVE-2022-1271 · CVE-2022-1304 · CVE-2022-1348 · CVE-2022-1586 · CVE-2022-1587 · CVE-2022-21824 · CVE-2022-2309 · CVE-2022-23540 · CVE-2022-23541 · CVE-2022-24903 · CVE-2022-2509 · CVE-2022-26280 · CVE-2022-27664 · CVE-2022-2795 · CVE-2022-2879 · CVE-2022-2880 · CVE-2022-28805 · CVE-2022-29154 · CVE-2022-30635 · CVE-2022-3094 · CVE-2022-31129 · CVE-2022-32189 · CVE-2022-32190 · CVE-2022-33099 · CVE-2022-3358 · CVE-2022-34903 · CVE-2022-3515 · CVE-2022-3517 · CVE-2022-35737 · CVE-2022-36227 · CVE-2022-3715 · CVE-2022-3736 · CVE-2022-37434 · CVE-2022-38149 · CVE-2022-3821 · CVE-2022-38900 · CVE-2022-3924 · CVE-2022-40023 · CVE-2022-40303 · CVE-2022-40304 · CVE-2022-40897 · CVE-2022-41316 · CVE-2022-41715 · CVE-2022-41717 · CVE-2022-41723 · CVE-2022-41724 · CVE-2022-41725 · CVE-2022-42010 · CVE-2022-42011 · CVE-2022-42012 · CVE-2022-42898 · CVE-2022-42919 · CVE-2022-43680 · CVE-2022-4415 · CVE-2022-45061 · CVE-2022-45873 · CVE-2022-46175 · CVE-2022-47024 · CVE-2022-47629 · CVE-2022-48303 · CVE-2022-48337 · CVE-2022-48338 · CVE-2022-48339 · CVE-2023-0361 · CVE-2023-0620 · CVE-2023-0665 · CVE-2023-22809 · CVE-2023-24329 · CVE-2023-2491 · CVE-2023-24999 · CVE-2023-25000 · CVE-2023-25136
- Source published
- Oct 11, 2022, 3:00:14 PM (timezone not stated)
- Source modified
- Sep 16, 2024, 4:33:30 PM (timezone not stated)
- Saved here
- 18 Nov 2026 03:29:42 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.