CVE-2025-9230

Out-of-bounds read & write in RFC 3211 KEK Unwrap

HIGH
7.5
CVSS Score
Published: September 30, 2025 at 01:17 PM UTC
Updated: October 15, 2026 at 02:18 AM UTC
20 products affected across 2 vendorsOpenSSLSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSIMATIC S7-1500 CPU 1518F 4 Pn /dp MFP Firmware

Using OpenSSL by OpenSSL?

Get instant alerts when new vulnerabilities affect OpenSSL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 2%
SSVC
No known exploit

Description

Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code. Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Affected range stops below 1.0.2zm, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.1zd, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.18, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.4, so it looks safe — our inference, not a vendor statement
v < V3.3v < V4.0
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
Affected range stops below V4.0, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement
v < V3.3
Affected range stops below V3.3, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHCISA-ADP
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-125CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card