CVE-2024-0727

PKCS12 Decoding crashes

MEDIUM
5.5
CVSS Score
Published: January 26, 2024 at 08:57 AM UTC
Updated: October 15, 2026 at 01:17 AM UTC
4 products affected across 2 vendorsOpenSSLSIMATIC S7-1500 TM MFPSINEC NMS

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
MEDIUM5.5
Exploit prediction
EPSS 3%
SSVC
No known exploit

Description

Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly. A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue. OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass(). We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.

Affected

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

1.0.2 ≤ v < 1.0.2zj1.1.1 ≤ v < 1.1.1x3.0.0 ≤ v < 3.0.133.1.0 ≤ v < 3.1.51.0.21.1.13.0.03.1.03.2.0
Affected range stops below 1.0.2zj, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.1x, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.1, so it looks safe — our inference, not a vendor statement
v < V4.0.700
Affected range stops below V4.0.700, so it looks safe — our inference, not a vendor statement
v < V3.0 SP1
Affected range stops below V3.0 SP1, 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

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476NVD-CWE-noinfo

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