CVE-2023-5363 Incorrect cipher key & IV length processing
Incorrect key and IV length processing in OpenSSL can cause IV truncation, leading to potential loss of confidentiality in specific cipher modes.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-5363?
CVE-2023-5363 is a high-severity vulnerability in Debian Debian Linux, published on 24 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Issue summary: A bug has been identified in the processing of key and initialisation vector (IV) lengths. This can lead to potential truncation or overruns during the initialisation of some symmetric ciphers.
Impact summary: A truncation in the IV can result in non-uniqueness, which could result in loss of confidentiality for some cipher modes.
When calling EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() or EVP_CipherInit_ex2() the provided OSSL_PARAM array is processed after the key and IV have been established. Any alterations to the key length, via the "keylen" parameter or the IV length, via the "ivlen" parameter, within the OSSL_PARAM array will not take effect as intended, potentially causing truncation or overreading of these values. The following ciphers and cipher modes are impacted: RC2, RC4, RC5, CCM, GCM and OCB.
For the CCM, GCM and OCB cipher modes, truncation of the IV can result in loss of confidentiality. For example, when following NIST's SP 800-38D section 8.2.1 guidance for constructing a deterministic IV for AES in GCM mode, truncation of the counter portion could lead to IV reuse.
Both truncations and overruns of the key and overruns of the IV will produce incorrect results and could, in some cases, trigger a memory exception. However, these issues are not currently assessed as security critical.
Changing the key and/or IV lengths is not considered to be a common operation and the vulnerable API was recently introduced. Furthermore it is likely that application developers will have spotted this problem during testing since decryption would fail unless both peers in the communication were similarly vulnerable. For these reasons we expect the probability of an application being vulnerable to this to be quite low. However if an application is vulnerable then this issue is considered very serious. For these reasons we have assessed this issue as Moderate severity overall.
The OpenSSL SSL/TLS implementation is not affected by this issue.
The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this because the issue lies outside of the FIPS provider boundary.
OpenSSL 3.1 and 3.0 are vulnerable to this issue.
Weakness: CWE-684
Which versions are affected by CVE-2023-5363?
It affects 7 products.
Linux distribution packages (25)
openssl AlmaLinux:9 | All versions | 1:3.0.7-25.el9_3 |
openssl-devel AlmaLinux:9 | All versions | 1:3.0.7-25.el9_3 |
openssl-libs AlmaLinux:9 | All versions | 1:3.0.7-25.el9_3 |
openssl-perl AlmaLinux:9 | All versions | 1:3.0.7-25.el9_3 |
openssl-debuginfo Red Hat:enterprise_linux:9::appstream | All versions | 1:3.0.7-25.el9_3 |
openssl-debugsource Red Hat:enterprise_linux:9::appstream | All versions | 1:3.0.7-25.el9_3 |
openssl-devel Red Hat:enterprise_linux:9::appstream | All versions | 1:3.0.7-25.el9_3 |
openssl-libs-debuginfo Red Hat:enterprise_linux:9::appstream | All versions | 1:3.0.7-25.el9_3 |
openssl-perl Red Hat:enterprise_linux:9::appstream | All versions | 1:3.0.7-25.el9_3 |
openssl Red Hat:enterprise_linux:9::baseos | All versions | 1:3.0.7-25.el9_3 |
openssl-debuginfo Red Hat:enterprise_linux:9::baseos | All versions | 1:3.0.7-25.el9_3 |
openssl-debugsource Red Hat:enterprise_linux:9::baseos | All versions | 1:3.0.7-25.el9_3 |
openssl-libs Red Hat:enterprise_linux:9::baseos | All versions | 1:3.0.7-25.el9_3 |
openssl-libs-debuginfo Red Hat:enterprise_linux:9::baseos | All versions | 1:3.0.7-25.el9_3 |
openssl-debuginfo Red Hat:rhel_eus:9.2::appstream | All versions | 1:3.0.7-18.el9_2 |
openssl-debugsource Red Hat:rhel_eus:9.2::appstream | All versions | 1:3.0.7-18.el9_2 |
openssl-devel Red Hat:rhel_eus:9.2::appstream | All versions | 1:3.0.7-18.el9_2 |
openssl-libs-debuginfo Red Hat:rhel_eus:9.2::appstream | All versions | 1:3.0.7-18.el9_2 |
openssl-perl Red Hat:rhel_eus:9.2::appstream | All versions | 1:3.0.7-18.el9_2 |
openssl Red Hat:rhel_eus:9.2::baseos | All versions | 1:3.0.7-18.el9_2 |
openssl-debuginfo Red Hat:rhel_eus:9.2::baseos | All versions | 1:3.0.7-18.el9_2 |
openssl-debugsource Red Hat:rhel_eus:9.2::baseos | All versions | 1:3.0.7-18.el9_2 |
openssl-libs Red Hat:rhel_eus:9.2::baseos | All versions | 1:3.0.7-18.el9_2 |
openssl-libs-debuginfo Red Hat:rhel_eus:9.2::baseos | All versions | 1:3.0.7-18.el9_2 |
openssl-3 openSUSE:Tumbleweed | All versions | 3.1.4-1.1 |
Products include Debian Debian Linux, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500s Firmware, Netapp H700s Firmware and 1 more.
How do I fix CVE-2023-5363?
Apply the vendor's patch.
Is CVE-2023-5363 being exploited?
There is no known exploitation of CVE-2023-5363 in the wild and no public exploit code.
Other vulnerabilities in Debian Debian Linux
Sources
Also known as ALPINE-CVE-2023-5363, ALSA-2024:0310, AZL-42712, AZL-42751, AZL-78558, BELL-CVE-2023-5363 and 13 more.