CVE-2024-9143

HIGHCVSS 8.8/10EPSS 9.00%

Last modified

CVE-2024-9143 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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. EPSS estimates a 9.00% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
9.00%

95.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
OpensslOpenssl>= 1.0.2, < 1.0.2zl
OpensslOpenssl>= 1.1.1, < 1.1.1zb
OpensslOpenssl>= 3.0.0, < 3.0.16
OpensslOpenssl>= 3.1.0, < 3.1.8
OpensslOpenssl>= 3.2.0, < 3.2.4
OpensslOpenssl>= 3.3.0, < 3.3.3
DebianDebian Linux11.0
NetappActive Iq Unified ManagerAll versions
NetappOntap Select Deploy Administration UtilityAll versions
NetappOntap ToolsAll versions
NetappSnapmanagerAll versions
NetappBrocade Fabric Operating SystemAll versions
NetappBootstrap OsAll versions
NetappA250 FirmwareAll versions
Netapp500f FirmwareAll versions
NetappC250 FirmwareAll versions
NetappH300s FirmwareAll versions
NetappH500s FirmwareAll versions
NetappH700s FirmwareAll versions
NetappH410s FirmwareAll versions
NetappH410c FirmwareAll versions
NetappH610c FirmwareAll versions
NetappH610s FirmwareAll versions
NetappH615c FirmwareAll versions
SiemensSimatic S7-1500 Tm Mfp Firmware< 1.1.1
SiemensSidis Prime< 4.0.700
SiemensSimatic S7-1500 Cpu 1518-4 Pn\/Dp Mfp Firmware>= 3.1.0, < 3.1.5
SiemensScalance Wab762-1 Firmware< 3.0.0
SiemensScalance Wam763-1 Firmware< 3.0.0
SiemensScalance Wam766-1 Firmware< 3.0.0
SiemensScalance Wub762-1 Firmware< 3.0.0
SiemensScalance Wub762-1 Ifeatures Firmware< 3.0.0
SiemensScalance Wum763-1 Firmware< 3.0.0
SiemensScalance Wum766-1 Firmware< 3.0.0

References

Timeline

Published
Last Modified
Status
Analyzed

Frequently Asked Questions

What is CVE-2024-9143?
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.
How severe is CVE-2024-9143?
CVE-2024-9143 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 9.00% probability of exploitation in the next 30 days.
How do I fix CVE-2024-9143?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2024

Are you affected by CVE-2024-9143?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST