CVE-2023-5363: Incorrect cipher key & IV length processing
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.9% (FIRST EPSS); higher than 90.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: OpenSSL OpenSSL 3.0.12, 3.1.4; Azure Linux 3.0 ARM 38.0.72.2-1; Azure Linux 3.0 x64 38.0.72.2-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to OpenSSL OpenSSL 3.0.12, 3.1.4; Azure Linux 3.0 ARM 38.0.72.2-1; Azure Linux 3.0 x64 38.0.72.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 25, 2023
- Updated
- Oct 14, 2026
- EPSS
- 3.9% · 90th percentile
- CWE
- CWE-684
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| netapp | h300s firmware | cpe:2.3:o:netapp:h300s_firmware |
| netapp | h300s | cpe:2.3:h:netapp:h300s |
| netapp | h410s firmware | cpe:2.3:o:netapp:h410s_firmware |
| netapp | h410s | cpe:2.3:h:netapp:h410s |
| netapp | h500s firmware | cpe:2.3:o:netapp:h500s_firmware |
| netapp | h500s | cpe:2.3:h:netapp:h500s |
| netapp | h700s firmware | cpe:2.3:o:netapp:h700s_firmware |
| netapp | h700s | cpe:2.3:h:netapp:h700s |
| netapp | h410c firmware | cpe:2.3:o:netapp:h410c_firmware |
| netapp | h410c | cpe:2.3:h:netapp:h410c |
Check your server's TLS configuration
The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux12.0
- netapp h300s firmwareall versions
- netapp h410c firmwareall versions
- netapp h410s firmwareall versions
- netapp h500s firmwareall versions
- netapp h700s firmwareall versions
- openssl openssl3.0.0 and later · before 3.0.12
- openssl openssl3.1.0 and later · before 3.1.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.
OpenSSL OpenSSL
- 3.0.0 and later · before 3.0.12affected · semver
- 3.1.0 and later · before 3.1.4affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | openssl | before 1:3.0.7-25.el9_3 | 1:3.0.7-25.el9_3 |
| AlmaLinux:9 | openssl-devel | before 1:3.0.7-25.el9_3 | 1:3.0.7-25.el9_3 |
| AlmaLinux:9 | openssl-libs | before 1:3.0.7-25.el9_3 | 1:3.0.7-25.el9_3 |
| AlmaLinux:9 | openssl-perl | before 1:3.0.7-25.el9_3 | 1:3.0.7-25.el9_3 |
| Alpine:v3.17 | openssl | from 3.0.0 · before 3.0.12-r0 | 3.0.12-r0 |
| Alpine:v3.18 | openssl | from 3.0.0 · before 3.1.4-r0 | 3.1.4-r0 |
| Debian:12 | openssl | before 3.0.11-1~deb12u2 | 3.0.11-1~deb12u2 |
| Debian:13 | openssl | before 3.0.12-1 | 3.0.12-1 |
| openSUSE:Leap 15.5 | openssl-3 | before 3.0.8-150500.5.14.1 | 3.0.8-150500.5.14.1 |
| openSUSE:Leap Micro 5.3 | openssl-3 | before 3.0.8-150400.4.37.1 | 3.0.8-150400.4.37.1 |
| openSUSE:Tumbleweed | openssl-3 | before 3.1.4-1.1 | 3.1.4-1.1 |
| Red Hat:enterprise_linux:9::appstream | openssl-debuginfo | before 1:3.0.7-25.el9_3 | 1:3.0.7-25.el9_3 |
| Red Hat:enterprise_linux:9::appstream | openssl-debugsource | before 1:3.0.7-25.el9_3 | 1:3.0.7-25.el9_3 |
| Red Hat:enterprise_linux:9::appstream | openssl-devel | before 1:3.0.7-25.el9_3 | 1:3.0.7-25.el9_3 |
| Red Hat:enterprise_linux:9::appstream | openssl-libs-debuginfo | before 1:3.0.7-25.el9_3 | 1:3.0.7-25.el9_3 |
| Red Hat:enterprise_linux:9::appstream | openssl-perl | before 1:3.0.7-25.el9_3 | 1:3.0.7-25.el9_3 |
| Red Hat:enterprise_linux:9::baseos | openssl | before 1:3.0.7-25.el9_3 | 1:3.0.7-25.el9_3 |
| Red Hat:enterprise_linux:9::baseos | openssl-libs | before 1:3.0.7-25.el9_3 | 1:3.0.7-25.el9_3 |
| Red Hat:rhel_eus:9.2::appstream | openssl-debuginfo | before 1:3.0.7-18.el9_2 | 1:3.0.7-18.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | openssl-debugsource | before 1:3.0.7-18.el9_2 | 1:3.0.7-18.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | openssl-devel | before 1:3.0.7-18.el9_2 | 1:3.0.7-18.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | openssl-libs-debuginfo | before 1:3.0.7-18.el9_2 | 1:3.0.7-18.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | openssl-perl | before 1:3.0.7-18.el9_2 | 1:3.0.7-18.el9_2 |
| Red Hat:rhel_eus:9.2::baseos | openssl | before 1:3.0.7-18.el9_2 | 1:3.0.7-18.el9_2 |
+3
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code 65This week
Published before and after this one in the same product
- ← EarlierCVE-2023-3817Jul 31, 2023 · Excessive time spent checking DH q parameter value22Monitor
- ← EarlierCVE-2023-4807Sep 8, 2023 · POLY1305 MAC implementation corrupts XMM registers on Windows31Monitor
- Later →CVE-2023-5678Nov 6, 2023 · Excessive time spent in DH check / generation with large Q parameter value23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| OpenSSL OpenSSL | 3.0.12 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.1.4 | Vendor (CNA) |
| Azure Linux 3.0 ARM | 38.0.72.2-1 · cloud-hypervisor-cvm | Microsoft (MSRC) |
| Azure Linux 3.0 x64 | 38.0.72.2-1 · cloud-hypervisor-cvm | Microsoft (MSRC) |
| CBL Mariner 2.0 ARM | 1.0.1-6 · hvloader | Microsoft (MSRC) |
| CBL Mariner 2.0 ARM | 18.20.2-1 · nodejs18 | Microsoft (MSRC) |
| CBL Mariner 2.0 ARM | 38.0.72.2-1 · cloud-hypervisor-cvm | Microsoft (MSRC) |
| CBL Mariner 2.0 x64 | 1.0.1-6 · hvloader | Microsoft (MSRC) |
| CBL Mariner 2.0 x64 | 18.20.2-1 · nodejs18 | Microsoft (MSRC) |
| CBL Mariner 2.0 x64 | 38.0.72.2-1 · cloud-hypervisor-cvm | Microsoft (MSRC) |
| almalinux:openssl | 1:3.0.7-25.el9_3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl-devel | 1:3.0.7-25.el9_3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl-libs | 1:3.0.7-25.el9_3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl-perl | 1:3.0.7-25.el9_3 · AlmaLinux:9 | Package registry (OSV) |
| alpine:openssl | 3.0.12-r0 · Alpine:v3.17 | Package registry (OSV) |
| debian:openssl | 3.0.11-1~deb12u2 · Debian:12 | Package registry (OSV) |
| opensuse:openssl-3 | 3.0.8-150400.4.37.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| red hat:openssl | 1:3.0.7-25.el9_3 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:openssl-debuginfo | 1:3.0.7-25.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-debugsource | 1:3.0.7-25.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-devel | 1:3.0.7-25.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-libs | 1:3.0.7-25.el9_3 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:openssl-libs-debuginfo | 1:3.0.7-25.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-perl | 1:3.0.7-25.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| suse:openssl-3 | 3.0.8-150400.4.37.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Tony Battersby (Cybernetics)finder
- Dr Paul Daleremediation developer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0602 · Oct 25, 2023(OpenSSL Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-684 · Incorrect Provision of Specified FunctionalityCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (13 more)Show less
- git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=5f69f5c65e483928c4b28ed16af6e5742929f1ee
- www.openssl.org/news/secadv/20231024.txt
- www.openwall.com/lists/oss-security/2023/10/24/1
- security.netapp.com/advisory/ntap-20231027-0010/
- security.netapp.com/advisory/ntap-20240201-0003/
- security.netapp.com/advisory/ntap-20240201-0004/
- security.netapp.com/advisory/ntap-20241108-0002/
- www.debian.org/security/2023/dsa-5532
- cert-portal.siemens.com/productcert/html/ssa-082556.html
- cert-portal.siemens.com/productcert/html/ssa-093430.html
- cert-portal.siemens.com/productcert/html/ssa-277137.html
- cert-portal.siemens.com/productcert/html/ssa-331112.html
- cert-portal.siemens.com/productcert/html/ssa-769027.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.