CVE-2023-5363
Incorrect cipher key & IV length processing
Reported by openssl · Published October 24, 2023
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| lib32-openssl | Arch Linux | 1:3.1.4-1 |
| openssl | Arch Linux | 3.1.4-1 |
| openssl | Wolfi | 3.1.4-r0 |
| openssl-snapsafe-libs | Amazon Linux | 1:3.0.8-1.amzn2023.0.9 |
| openssl-libs | Amazon Linux | 1:3.0.8-1.amzn2023.0.9 |
| openssl-devel | Amazon Linux | 1:3.0.8-1.amzn2023.0.9 |
| openssl | conan.io | 3.1.4, 3.0.12 |
| openssl | Amazon Linux | 1:3.0.8-1.amzn2023.0.9 |
| openssl | Chainguard | 3.1.4-r0 |
| openssl | Alpine | 3.1.4-r0, 3.0.12-r0 |
| openssl-perl | Amazon Linux | 1:3.0.8-1.amzn2023.0.9 |
| OpenSSL | OpenSSL | 3.1.4, 3.0.12 |
2 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| OpenSSL | OpenSSL | 3.0.0, 3.1.0 |
| arch | lib32-openssl | 0 |
| arch | openssl | 0 |
| chainguard | openssl-provider-fips | * |
| Siemens | SIPLUS S7-1500 CPU 1518-4 PN/DP MFP | 3.1.5 |
| OpenSSL | OpenSSL | 3.0.0, 3.1.0 |
| wolfi | openssl | 0 |
| chainguard | openssl-provider-fips-3.1.2 | * |
| amazon:2023 | openssl-snapsafe-libs | 0 |
| amazon:2023 | openssl-libs | 0 |
| amazon:2023 | openssl-devel | 0 |
| Siemens | SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP | 3.1.5 |
| Siemens | SIDIS Prime | 0 |
| Siemens | SIMATIC S7-1500 CPU 1518-4 PN/DP MFP | 3.1.5 |
| Siemens | SINEC NMS | 0 |
| amazon:2023 | openssl | 0 |
| ConanCenter | openssl | 3.1.0, 3.0.0 |
| wolfi | ruby-3.2 | * |
| chainguard | openssl | 0 |
| alpine | openssl | 0, 0 |
…and 2 more
Timeline
- Oct 24, 2023 CVE Published
- Oct 25, 2023 EPSS Score (30 in total, the first dated here)
- Oct 5, 2024 Coalition ESS Score (30 in total, the first dated here)
- Dec 18, 2025 PoC Published
- Jan 24, 2026 Distribution Patch (13 in total, the first dated here)
- Jan 24, 2026 Security Advisory (20 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2023-5363
vulnetix vdb fixes CVE-2023-5363
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2023-5363/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- OpenSSL Advisory vendor-advisory
- 3.1.4 git commit patch
- 3.0.12 git commit patch
- https://nvd.nist.gov/vuln/detail/CVE-2023-5363 advisory
- http://www.openwall.com/lists/oss-security/2023/10/24/1 url
- https://www.debian.org/security/2023/dsa-5532 url
- https://security.netapp.com/advisory/ntap-20231027-0010/ url
- https://security.netapp.com/advisory/ntap-20240201-0003/ url
- https://security.netapp.com/advisory/ntap-20240201-0004/ url
- https://security.netapp.com/advisory/ntap-20241108-0002/ url
- https://cert-portal.siemens.com/productcert/html/ssa-093430.html url
- https://cert-portal.siemens.com/productcert/html/ssa-331112.html url
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html url
- https://cert-portal.siemens.com/productcert/html/ssa-277137.html url
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html url