Skip to main content
VulnerabilityPublished Updated

CVE-2024-9143: OpenSSL · Out-of-bounds Read

Affects OpenSSLSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.8 High.

Data as of 6 Nov 2026, 23:23 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.18.8
EPSS
5.8% chance of exploitation in 30 days – higher than 93% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
OpenSSL OpenSSLAffected
  • 1.0.2 – 3.3.0
  • 3.3.0
  • 3.2.0
  • 3.1.0
  • 3.0.0
  • 1.1.1
  • 1.0.2
6 affected builds
Fixed in–

AI-suggested

Users should avoid using explicit binary (GF(2^m)) curve parameters with untrusted input, especially those that could specify invalid field polynomials. Since common protocols and FIPS modules are not affected, no urgent action is required for typical deployments. Monitor vendor advisories for any updates or patches.

Description

CVE-2024-9143 is an out-of-bounds read and write vulnerability in OpenSSL's low-level GF(2^m) elliptic curve APIs when used with untrusted explicit field polynomial values. This can cause application crashes and potentially remote code execution, but only in rare cases involving exotic curve encodings. Standard protocols using named curves or X9.62 encoding for ECC keys in X.509 certificates are not affected. The FIPS modules are also unaffected.

References

Community reviews

Loading reviews…