Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2023-5363

openssl: Incorrect cipher key and IV length processing

Overview

Published
25 Oct 2023
Modified
17 Jun 2026
High CVE
2 Registry packages
24 OS packages
20 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Weakness: CWE-684

Affected packages · 2

Packages affected by CVE-2023-5363
EcosystemPackageVulnerableFixed in
Conan (C/C++) openssl >=3.0.0 <3.0.12||>=3.1.0 <3.1.4 3.0.123.1.4
Julia OpenSSL_jll >=3.0.8+0, <3.0.12+0 3.0.12+0

Open a package to see all its vulnerabilities.

Operating systems · 42 fixes

Azure Linux 1 release · 1 package

fixed 1
cloud-hypervisor-cvm
Azure Linux fixes for CVE-2023-5363
ReleasePackageFixed in
3.0 cloud-hypervisor-cvm 0:38.0.72.2-1.azl3

Oracle Linux 1 release · 1 package

fixed 2
openssl
Oracle Linux fixes for CVE-2023-5363
ReleasePackageFixed in
9 openssl +3 1:3.0.7-25.0.1.el9_3
9 openssl +3 2:3.0.7-25.0.1.ksplice1.el9_3

Photon OS 2 releases · 1 package

fixed 2
openssl
Photon OS fixes for CVE-2023-5363
ReleasePackageFixed in
4.0 openssl +4 3.0.9-7.ph4
5.0 openssl +5 3.0.9-7.ph5

Red Hat 1 release · 1 package

fixed 2
openssl
Red Hat fixes for CVE-2023-5363
ReleasePackageFixed inAdvisory
9 openssl +3 1:3.0.7-18.el9_2 RHSA-2024:0500
9 openssl +3 1:3.0.7-25.el9_3 RHSA-2024:0310

SUSE Linux Enterprise 2 releases · 1 package

fixed 2
libopenssl-3-devel
SUSE Linux Enterprise fixes for CVE-2023-5363
ReleasePackageFixed inAdvisory
15.4 libopenssl-3-devel +2 3.0.8-150400.4.37.1 SUSE-SU-2023:4189-1
15.5 libopenssl-3-devel +2 3.0.8-150500.5.14.1 SUSE-SU-2023:4190-1

SUSE Linux Enterprise Micro 2 releases · 1 package

fixed 2
libopenssl3
SUSE Linux Enterprise Micro fixes for CVE-2023-5363
ReleasePackageFixed inAdvisory
5.3 libopenssl3 3.0.8-150400.4.37.1 SUSE-SU-2023:4189-1
5.4 libopenssl3 3.0.8-150400.4.37.1 SUSE-SU-2023:4189-1

alma 1 release · 1 package

fixed 1
openssl
alma fixes for CVE-2023-5363
ReleasePackageFixed in
9 openssl +3 1:3.0.7-25.el9_3

alpine 4 releases · 1 package

fixed 4
openssl
alpine fixes for CVE-2023-5363
ReleasePackageFixed in
3.22 openssl 3.1.4-r0
3.23 openssl 3.1.4-r0
3.24 openssl 3.1.4-r0
edge openssl 3.1.4-r0

amazon linux 1 release · 1 package

fixed 1
openssl
amazon linux fixes for CVE-2023-5363
ReleasePackageFixed in
2023 openssl +8 1:3.0.8-1.amzn2023.0.9

chainguard 1 release · 2 packages

not affected 1 fixed 1
openssl-provider-fips openssl
chainguard fixes for CVE-2023-5363
ReleasePackageFixed in
openssl-provider-fips +2 not affected
openssl 3.1.4-r0

debian 3 releases · 1 package

fixed 3
openssl
debian fixes for CVE-2023-5363
ReleasePackageFixed in
12 openssl 3.0.11-1~deb12u2
13 openssl 3.0.12-1
14 openssl 3.0.12-1

echo 1 release · 3 packages

fixed 3
openssl openssl-3-0-9 openssl-3-1-0
echo fixes for CVE-2023-5363
ReleasePackageFixed in
openssl 3.0.11-1~deb12u2
openssl-3-0-9 3.0.9+e1
openssl-3-1-0 3.1.0+e1

openSUSE 1 release · 1 package

fixed 1
libopenssl-3-devel
openSUSE fixes for CVE-2023-5363
ReleasePackageFixed inAdvisory
Tumbleweed libopenssl-3-devel +6 3.1.4-1.1 openSUSE-SU-2024:13372-1

openSUSE Leap Micro 2 releases · 1 package

fixed 2
libopenssl3
openSUSE Leap Micro fixes for CVE-2023-5363
ReleasePackageFixed inAdvisory
5.3 libopenssl3 3.0.8-150400.4.37.1 SUSE-SU-2023:4189-1
5.4 libopenssl3 3.0.8-150400.4.37.1 SUSE-SU-2023:4189-1

root.io alpine 1 release · 1 package

fixed 1
rootio-openssl
root.io alpine fixes for CVE-2023-5363
ReleasePackageFixed in
3.23 rootio-openssl 3.1.4-r0

root.io debian 1 release · 1 package

fixed 1
rootio-openssl
root.io debian fixes for CVE-2023-5363
ReleasePackageFixed in
12 rootio-openssl 3.0.11-1~deb12u2

seal Red Hat 2 releases · 1 package

fixed 4
openssl
seal Red Hat fixes for CVE-2023-5363
ReleasePackageFixed in
7 openssl +1 1:1.0.2k-25.el7_9+sp999
7 openssl +1 1:1.0.2k-26.el7_9+sp999
8 openssl +1 1:1.1.1k-14.el8_6+sp999
8 openssl +1 1:1.1.1k-6.el8_5+sp999

seal debian 1 release · 1 package

fixed 2
openssl
seal debian fixes for CVE-2023-5363
ReleasePackageFixed in
openssl +1 1.1.1w-0+deb11u2+sp999
openssl +1 3.0.11-1~deb12u2+sp999

ubuntu 3 releases · 2 packages

affected 1 fixed 3
nodejs openssl
ubuntu fixes for CVE-2023-5363
ReleasePackageFixed in
22.04 nodejs affected
22.04 openssl 3.0.2-0ubuntu1.12
24.04 openssl 3.0.10-1ubuntu2.1
26.04 openssl 3.0.10-1ubuntu2.1

wolfi 1 release · 2 packages

not affected 1 fixed 1
ruby-3-2 openssl
wolfi fixes for CVE-2023-5363
ReleasePackageFixed in
ruby-3-2 not affected
openssl 3.1.4-r0

References

Show all 28 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.