CVE-2024-9143 is a vulnerability in OpenSSL’s low-level binary-field elliptic curve handling. When applications use low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial, invalid parameters can trigger out-of-bounds memory reads or writes. The issue affects APIs including EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and supporting BN_GF2m_*() routines. The vulnerable condition arises when an application accepts explicit binary curve parameters that permit an invalid field polynomial with a zero constant term, leading to incorrect bounds handling during polynomial processing. OpenSSL indicated that common ECC protocol usage is generally not exposed because named curves are typically used, and X9.62 encodings for binary curves cannot represent the problematic inputs, including in X.509 certificate processing. The OpenSSL FIPS modules in the 3.3, 3.2, 3.1, and 3.0 branches are not affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability in OpenSSL cited as one of the AI-assisted vulnerability reports produced via Google OSS-Fuzz AI.
An OpenSSL vulnerability reportedly found via LLM-generated fuzz targets according to Google OSS-Fuzz.
A possible out-of-bounds memory access vulnerability in OpenSSL when handling invalid low-level GF(2^m) elliptic curve parameters.
A possible out-of-bounds memory access vulnerability involving invalid low-level GF(2^m) elliptic curve parameters in OpenSSL.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.