CVE-2024-0727: OpenSSL · NULL Pointer Dereference
Affects OpenSSLSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 3.1% chance of exploitation in 30 days – higher than 87% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubopenssl/opensslpkg:github/openssl/opensslOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a patch is applied, avoid processing PKCS12 files from untrusted sources using the vulnerable OpenSSL APIs. The FIPS modules in versions 3.0, 3.1, and 3.2 are not affected and can be used as a mitigation if applicable.
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.
References
- openssl.org/news/secadv/20240125.txt (opens in a new tab)
- github.com/openssl/openssl/commit/775acfdbd0c6af9ac855f34969cdab0c0c90844a (opens in a new tab)
- github.com/openssl/openssl/commit/d135eeab8a5dbf72b3da5240bab9ddb7678dbd2c (opens in a new tab)
- github.com/openssl/openssl/commit/09df4395b5071217b76dc7d3d2e630eb8c5a79c2 (opens in a new tab)
- github.openssl.org/openssl/extended-releases/commit/03b3941d60c4bce58fab69a0c22377ab439bc0e8 (opens in a new tab)
- github.openssl.org/openssl/extended-releases/commit/aebaa5883e31122b404e450732dc833dc9dee539 (opens in a new tab)
- security.netapp.com/advisory/ntap-20240208-0006/ (opens in a new tab)
- openwall.com/lists/oss-security/2024/03/11/1 (opens in a new tab)