CVE-2025-69421: NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex function
Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer
dereference in the PKCS12_item_decrypt_d2i_ex() function.
Impact summary: A NULL pointer dereference can trigger a crash which leads to
Denial of Service for an application processing PKCS#12 files.
The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct
parameter is NULL before dereferencing it. When called from
PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can
be NULL, causing a crash. The vulnerability is limited to Denial of Service
and cannot be escalated to achieve code execution or memory disclosure.
Exploiting this issue requires an attacker to provide a malformed PKCS#12 file
to an application that processes it. For that reason the issue was assessed as
Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,
as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Security readout for executives and security teams
Plain-English summary
A malformed PKCS#12 certificate file can crash applications that use vulnerable OpenSSL versions to process it. The known impact is denial of service: the application may stop handling work. Sources state it cannot be escalated to code execution or memory disclosure. No KEV listing is provided.
Executive priority
Treat this as a targeted availability risk, not a breach-class issue. Patch normal maintenance lanes, but accelerate remediation for internet-facing or partner-facing certificate import services where a crash could disrupt operations.
Technical view
PKCS12_item_decrypt_d2i_ex() can dereference a NULL oct parameter when reached via PKCS12_unpack_p7encdata() during malformed PKCS#12 parsing. This is CWE-476 and affects OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1, and 1.0.2. FIPS modules listed by OpenSSL are not affected.
Likely exposure
Exposure is most likely where applications accept or import PKCS#12 files from users, partners, devices, or automated certificate workflows. Systems that do not parse untrusted PKCS#12 input have lower practical exposure, even if OpenSSL is present.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. Exploitation requires supplying a malformed PKCS#12 file to an application that processes it. The documented outcome is a crash causing denial of service, not code execution or data disclosure.
Researcher notes
The advisory explicitly limits impact to denial of service and says escalation to code execution or memory disclosure is not possible. CVSS 3.1 is 7.5 for availability, while OpenSSL assessed the issue as Low under its policy because attacker-controlled PKCS#12 processing is required.
Mitigation direction
Upgrade OpenSSL to the vendor-fixed release for the deployed branch.
Prioritize services that parse externally supplied PKCS#12 files.
Check vendor advisories for appliance or embedded product updates.
Restrict PKCS#12 import paths to trusted users where feasible.
Monitor affected services for crash loops during certificate import workflows.
Validation and detection
Inventory OpenSSL versions across applications, containers, appliances, and build images.
Identify code paths that call OpenSSL PKCS#12 parsing on external input.
Confirm deployed packages include the relevant OpenSSL patch commit or fixed release.
Review crash telemetry for certificate import or PKCS#12 processing failures.
Track Siemens and other downstream advisories if their products are deployed.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.