Skip to main content
No exploitation reportedFix available

CVE-2024-0727

No exploitation reported by the sources we read.

  • Published2024-01-26
  • Fixed in3.1.5 · 3.0.13 · 1.1.1x · 1.0.2zj
  • WeaknessCWE-476

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2024-01-2609:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-0727?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-0727?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
OpenSSL
BranchAffectedFixed in
3.1≥ 3.1.0, < 3.1.53.1.5
3.0≥ 3.0.0, < 3.0.133.0.13
1.1≥ 1.1.1, < 1.1.1x1.1.1x
1.0≥ 1.0.2, < 1.0.2zj1.0.2zj
3.2= 3.2.0no fix published
cryptography
BranchAffectedFixed in
42.0< 42.0.242.0.2

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • edk2-toolsAlmaLinux:9all versions · fixed in 20240524-6.el9_5and 3 other packages
  • opensslAlmaLinux:9all versions · fixed in 1:3.0.7-27.el9and 3 other packages

Vendor advisories

  • ICSA-24-275-02 CISA1 known affected

    Mitsubishi Electric MELSEC iQ-F FX5-OPC

    Mitsubishi Electric MELSEC iQ-F FX5-OPC: vers:all/*

Full record on NVD

Fix

  1. Update OpenSSL to 3.1.5 · 3.0.13 · 1.1.1x · 1.0.2zj
  2. Mitigation from the vendor CISA ICSA-24-275-02 · 1 productMitsubishi Electric recommends that customers take the following mitigations to minimize the risk of exploiting this vulnerability:
  3. Mitigation from the vendor CISA ICSA-24-275-02 · 1 productUse within a LAN and block access from untrusted networks and hosts through firewalls.
  4. Mitigation from the vendor CISA ICSA-24-275-02 · 1 productRestrict physical access to the product, as well as to computers and network devices located within the same network as the product.
  5. Mitigation from the vendor CISA ICSA-24-275-02 · 1 productUse a firewall or virtual private network (VPN), etc. to prevent unauthorized access when Internet access is required.
  6. Mitigation from the vendor CISA ICSA-24-275-02 · 1 productUse IP filter function to block access from untrusted hosts. For details on the IP filter function, please refer to the following manual. MELSEC iQ-F FX5 OPC UA Module User's Manual "4.4 IP Filter"
  7. Mitigation from the vendor CISA ICSA-24-275-02 · 1 productDo not import untrusted certificates.

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2025-05-08
  • OpenCVESSVC decisionnone—
  • CISA-ADPCVSS 3.15.52025-05-08
  • NVDCVSS 3.15.5read 2026-10-23
  • CISA-ADPweakness (CWE)CWE-4762025-05-08
  • CNAweakness (CWE)CWE-476read 2026-10-23
  • FIRST EPSSEPSS score3.2 %2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Published
2024-01-26
Last Modified
2026-10-15
NVD status
Modified

Frequently asked questions

What is CVE-2024-0727?

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.

Is CVE-2024-0727 actively exploited?

Active exploitation of CVE-2024-0727 has not been confirmed. Its EPSS score was 3.2% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-0727?

CVE-2024-0727 has a CVSS v3 base score of 5.5 (MEDIUM severity), with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H.

Running OpenSSL? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month