boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Thursday, November 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2024-9143

OpenSSL OpenSSL — Low-level invalid GF(2^m) parameters lead to OOB memory access
  AV  AC  PR  UI  S  C  I  A   CVSS    EPSS   %ile   KEV
   N   L   L   N  U  H  H  H    8.8   .1248   96.3     —
AFFECTED
  Product  Versions  Fixed
  OpenSSL  3.3.0 –   —
TIMELINE
  Sep 24  Reserved by openssl
  Oct 16  Published (CNA: openssl)
  Nov 6   RESCORED — CVE-2024-9143 (OpenSSL). CVSS 4.3 → 8.8 (NVD).
CWE-125, CWE-787 · CNA: openssl · CVSS v3.1 · 17 references · NVD status: Analyzed

Description

Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding. The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions. Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Lifecycle

Complete event history — 3 events, chronological
DateEventDetail
September 24, 2024ReservedReserved by openssl
October 16, 2024PublishedPublished (CNA: openssl)
November 6, 2026RESCOREDRESCORED — CVE-2024-9143 (OpenSSL). CVSS 4.3 → 8.8 (NVD).

Affected

Affected products and packages — 1 row
VendorProduct / PackageEcosystemVersion introducedFixed
OpenSSLOpenSSL—3.3.0—

Weaknesses

CWE-125 · CWE-787

References (17)

Related

Authoritative record: CVE-2024-9143 at cve.org

Vendors: openssl

Weaknesses: CWE-125 · CWE-787

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2024-9143 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Thursday, November 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.