{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2024-9143", "assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "state": "PUBLISHED", "assignerShortName": "openssl", "dateReserved": "2024-09-24T08:37:04.834Z", "datePublished": "2024-10-16T17:09:23.844Z", "dateUpdated": "2025-11-03T22:33:18.178Z"}, "containers": {"cna": {"affected": [{"defaultStatus": "unaffected", "product": "OpenSSL", "vendor": "OpenSSL", "versions": [{"lessThan": "3.3.3", "status": "affected", "version": "3.3.0", "versionType": "semver"}, {"lessThan": "3.2.4", "status": "affected", "version": "3.2.0", "versionType": "semver"}, {"lessThan": "3.1.8", "status": "affected", "version": "3.1.0", "versionType": "semver"}, {"lessThan": "3.0.16", "status": "affected", "version": "3.0.0", "versionType": "semver"}, {"lessThan": "1.1.1zb", "status": "affected", "version": "1.1.1", "versionType": "custom"}, {"lessThan": "1.0.2zl", "status": "affected", "version": "1.0.2", "versionType": "custom"}]}], "credits": [{"lang": "en", "type": "finder", "value": "Google OSS-Fuzz-Gen"}, {"lang": "en", "type": "remediation developer", "value": "Viktor Dukhovni"}], "datePublic": "2024-10-16T14:00:00.000Z", "descriptions": [{"lang": "en", "supportingMedia": [{"base64": false, "type": "text/html", "value": "Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted<br>explicit values for the field polynomial can lead to out-of-bounds memory reads<br>or writes.<br><br>Impact summary: Out of bound memory writes can lead to an application crash or<br>even a possibility of a remote code execution, however, in all the protocols<br>involving Elliptic Curve Cryptography that we're aware of, either only \"named<br>curves\" are supported, or, if explicit curve parameters are supported, they<br>specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent<br>problematic input values. Thus the likelihood of existence of a vulnerable<br>application is low.<br><br>In particular, the X9.62 encoding is used for ECC keys in X.509 certificates,<br>so problematic inputs cannot occur in the context of processing X.509<br>certificates. Any problematic use-cases would have to be using an \"exotic\"<br>curve encoding.<br><br>The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),<br>and various supporting BN_GF2m_*() functions.<br><br>Applications working with \"exotic\" explicit binary (GF(2^m)) curve parameters,<br>that make it possible to represent invalid field polynomials with a zero<br>constant term, via the above or similar APIs, may terminate abruptly as a<br>result of reading or writing outside of array bounds. Remote code execution<br>cannot easily be ruled out.<br><br>The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue."}], "value": "Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted\nexplicit values for the field polynomial can lead to out-of-bounds memory reads\nor writes.\n\nImpact summary: Out of bound memory writes can lead to an application crash or\neven a possibility of a remote code execution, however, in all the protocols\ninvolving Elliptic Curve Cryptography that we're aware of, either only \"named\ncurves\" are supported, or, if explicit curve parameters are supported, they\nspecify an X9.62 encoding of binary (GF(2^m)) curves that can't represent\nproblematic input values. Thus the likelihood of existence of a vulnerable\napplication is low.\n\nIn particular, the X9.62 encoding is used for ECC keys in X.509 certificates,\nso problematic inputs cannot occur in the context of processing X.509\ncertificates. Any problematic use-cases would have to be using an \"exotic\"\ncurve encoding.\n\nThe affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),\nand various supporting BN_GF2m_*() functions.\n\nApplications working with \"exotic\" explicit binary (GF(2^m)) curve parameters,\nthat make it possible to represent invalid field polynomials with a zero\nconstant term, via the above or similar APIs, may terminate abruptly as a\nresult of reading or writing outside of array bounds. Remote code execution\ncannot easily be ruled out.\n\nThe FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue."}], "metrics": [{"format": "other", "other": {"content": {"text": "Low"}, "type": "https://openssl-library.org/policies/general/security-policy/"}}], "problemTypes": [{"descriptions": [{"cweId": "CWE-125", "description": "CWE-125 Out-of-bounds Read", "lang": "en", "type": "CWE"}, {"cweId": "CWE-787", "description": "CWE-787 Out-of-bounds Write", "lang": "en", "type": "CWE"}]}], "providerMetadata": {"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "shortName": "openssl", "dateUpdated": "2025-09-01T08:29:10.392Z"}, "references": [{"name": "OpenSSL Advisory", "tags": ["vendor-advisory"], "url": "https://openssl-library.org/news/secadv/20241016.txt"}, {"name": "3.3.3 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/c0d3e4d32d2805f49bec30547f225bc4d092e1f4"}, {"name": "3.2.4 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/bc7e04d7c8d509fb78fc0e285aa948fb0da04700"}, {"name": "3.1.8 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/fdf6723362ca51bd883295efe206cb5b1cfa5154"}, {"name": "3.0.16 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/72ae83ad214d2eef262461365a1975707f862712"}, {"name": "1.1.1zb git commit", "tags": ["patch"], "url": "https://github.openssl.org/openssl/extended-releases/commit/8efc0cbaa8ebba8e116f7b81a876a4123594d86a"}, {"name": "1.0.2zl git commit", "tags": ["patch"], "url": "https://github.openssl.org/openssl/extended-releases/commit/9d576994cec2b7aa37a91740ea7e680810957e41"}], "source": {"discovery": "UNKNOWN"}, "title": "Low-level invalid GF(2^m) parameters lead to OOB memory access", "x_generator": {"engine": "Vulnogram 0.2.0"}}, "adp": [{"metrics": [{"cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}}, {"other": {"type": "ssvc", "content": {"timestamp": "2024-10-16T19:45:11.544020Z", "id": "CVE-2024-9143", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2024-11-08T15:30:04.030Z"}}, {"title": "CVE Program Container", "references": [{"url": "http://www.openwall.com/lists/oss-security/2024/10/16/1"}, {"url": "http://www.openwall.com/lists/oss-security/2024/10/23/1"}, {"url": "http://www.openwall.com/lists/oss-security/2024/10/24/1"}, {"url": "https://security.netapp.com/advisory/ntap-20241101-0001/"}, {"url": "https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html"}, {"url": "https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html"}], "providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2025-11-03T22:33:18.178Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CVE Program Container", "references": [{"url": "http://www.openwall.com/lists/oss-security/2024/10/16/1"}, {"url": "http://www.openwall.com/lists/oss-security/2024/10/23/1"}, {"url": "http://www.openwall.com/lists/oss-security/2024/10/24/1"}, {"url": "https://security.netapp.com/advisory/ntap-20241101-0001/"}], "providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-11-01T17:03:16.065Z"}}, {"title": "CISA ADP Vulnrichment", "metrics": [{"cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}}, {"other": {"type": "ssvc", "content": {"id": "CVE-2024-9143", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2024-10-16T19:45:11.544020Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2024-10-16T19:45:18.967Z"}}], "cna": {"title": "Low-level invalid GF(2^m) parameters lead to OOB memory access", "source": {"discovery": "UNKNOWN"}, "credits": [{"lang": "en", "type": "finder", "value": "Google OSS-Fuzz-Gen"}, {"lang": "en", "type": "remediation developer", "value": "Viktor Dukhovni"}], "metrics": [{"other": {"type": "https://openssl-library.org/policies/general/security-policy/", "content": {"text": "Low"}}, "format": "other"}], "affected": [{"vendor": "OpenSSL", "product": "OpenSSL", "versions": [{"status": "affected", "version": "3.3.0", "lessThan": "3.3.3", "versionType": "semver"}, {"status": "affected", "version": "3.2.0", "lessThan": "3.2.4", "versionType": "semver"}, {"status": "affected", "version": "3.1.0", "lessThan": "3.1.8", "versionType": "semver"}, {"status": "affected", "version": "3.0.0", "lessThan": "3.0.16", "versionType": "semver"}, {"status": "affected", "version": "1.1.1", "lessThan": "1.1.1zb", "versionType": "custom"}, {"status": "affected", "version": "1.0.2", "lessThan": "1.0.2zl", "versionType": "custom"}], "defaultStatus": "unaffected"}], "datePublic": "2024-10-16T14:00:00.000Z", "references": [{"url": "https://openssl-library.org/news/secadv/20241016.txt", "name": "OpenSSL Advisory", "tags": ["vendor-advisory"]}, {"url": "https://github.com/openssl/openssl/commit/c0d3e4d32d2805f49bec30547f225bc4d092e1f4", "name": "3.3.3 git commit", "tags": ["patch"]}, {"url": "https://github.com/openssl/openssl/commit/bc7e04d7c8d509fb78fc0e285aa948fb0da04700", "name": "3.2.4 git commit", "tags": ["patch"]}, {"url": "https://github.com/openssl/openssl/commit/fdf6723362ca51bd883295efe206cb5b1cfa5154", "name": "3.1.8 git commit", "tags": ["patch"]}, {"url": "https://github.com/openssl/openssl/commit/72ae83ad214d2eef262461365a1975707f862712", "name": "3.0.16 git commit", "tags": ["patch"]}, {"url": "https://github.openssl.org/openssl/extended-releases/commit/8efc0cbaa8ebba8e116f7b81a876a4123594d86a", "name": "1.1.1zb git commit", "tags": ["patch"]}, {"url": "https://github.openssl.org/openssl/extended-releases/commit/9d576994cec2b7aa37a91740ea7e680810957e41", "name": "1.0.2zl git commit", "tags": ["patch"]}], "x_generator": {"engine": "Vulnogram 0.2.0"}, "descriptions": [{"lang": "en", "value": "Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted\nexplicit values for the field polynomial can lead to out-of-bounds memory reads\nor writes.\n\nImpact summary: Out of bound memory writes can lead to an application crash or\neven a possibility of a remote code execution, however, in all the protocols\ninvolving Elliptic Curve Cryptography that we're aware of, either only \"named\ncurves\" are supported, or, if explicit curve parameters are supported, they\nspecify an X9.62 encoding of binary (GF(2^m)) curves that can't represent\nproblematic input values. Thus the likelihood of existence of a vulnerable\napplication is low.\n\nIn particular, the X9.62 encoding is used for ECC keys in X.509 certificates,\nso problematic inputs cannot occur in the context of processing X.509\ncertificates. Any problematic use-cases would have to be using an \"exotic\"\ncurve encoding.\n\nThe affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),\nand various supporting BN_GF2m_*() functions.\n\nApplications working with \"exotic\" explicit binary (GF(2^m)) curve parameters,\nthat make it possible to represent invalid field polynomials with a zero\nconstant term, via the above or similar APIs, may terminate abruptly as a\nresult of reading or writing outside of array bounds. Remote code execution\ncannot easily be ruled out.\n\nThe FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.", "supportingMedia": [{"type": "text/html", "value": "Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted<br>explicit values for the field polynomial can lead to out-of-bounds memory reads<br>or writes.<br><br>Impact summary: Out of bound memory writes can lead to an application crash or<br>even a possibility of a remote code execution, however, in all the protocols<br>involving Elliptic Curve Cryptography that we're aware of, either only \"named<br>curves\" are supported, or, if explicit curve parameters are supported, they<br>specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent<br>problematic input values. Thus the likelihood of existence of a vulnerable<br>application is low.<br><br>In particular, the X9.62 encoding is used for ECC keys in X.509 certificates,<br>so problematic inputs cannot occur in the context of processing X.509<br>certificates. Any problematic use-cases would have to be using an \"exotic\"<br>curve encoding.<br><br>The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),<br>and various supporting BN_GF2m_*() functions.<br><br>Applications working with \"exotic\" explicit binary (GF(2^m)) curve parameters,<br>that make it possible to represent invalid field polynomials with a zero<br>constant term, via the above or similar APIs, may terminate abruptly as a<br>result of reading or writing outside of array bounds. Remote code execution<br>cannot easily be ruled out.<br><br>The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.", "base64": false}]}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-125", "description": "CWE-125 Out-of-bounds Read"}, {"lang": "en", "type": "CWE", "cweId": "CWE-787", "description": "CWE-787 Out-of-bounds Write"}]}], "providerMetadata": {"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "shortName": "openssl", "dateUpdated": "2025-09-01T08:29:10.392Z"}}}, "cveMetadata": {"cveId": "CVE-2024-9143", "state": "PUBLISHED", "dateUpdated": "2025-09-01T08:29:10.392Z", "dateReserved": "2024-09-24T08:37:04.834Z", "assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "datePublished": "2024-10-16T17:09:23.844Z", "assignerShortName": "openssl"}, "dataVersion": "5.1"}

{"cveTags": [], "descriptions": [{"lang": "en", "value": "Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted\nexplicit values for the field polynomial can lead to out-of-bounds memory reads\nor writes.\n\nImpact summary: Out of bound memory writes can lead to an application crash or\neven a possibility of a remote code execution, however, in all the protocols\ninvolving Elliptic Curve Cryptography that we're aware of, either only \"named\ncurves\" are supported, or, if explicit curve parameters are supported, they\nspecify an X9.62 encoding of binary (GF(2^m)) curves that can't represent\nproblematic input values. Thus the likelihood of existence of a vulnerable\napplication is low.\n\nIn particular, the X9.62 encoding is used for ECC keys in X.509 certificates,\nso problematic inputs cannot occur in the context of processing X.509\ncertificates. Any problematic use-cases would have to be using an \"exotic\"\ncurve encoding.\n\nThe affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),\nand various supporting BN_GF2m_*() functions.\n\nApplications working with \"exotic\" explicit binary (GF(2^m)) curve parameters,\nthat make it possible to represent invalid field polynomials with a zero\nconstant term, via the above or similar APIs, may terminate abruptly as a\nresult of reading or writing outside of array bounds. Remote code execution\ncannot easily be ruled out.\n\nThe FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue."}, {"lang": "es", "value": "Resumen del problema: el uso de las API de curva el\u00edptica GF(2^m) de bajo nivel con valores expl\u00edcitos no confiables para el campo polinomial puede generar lecturas o escrituras de memoria fuera de los l\u00edmites. Resumen del impacto: las escrituras de memoria fuera de los l\u00edmites pueden generar un bloqueo de la aplicaci\u00f3n o incluso la posibilidad de una ejecuci\u00f3n de c\u00f3digo remoto; sin embargo, en todos los protocolos que involucran criptograf\u00eda de curva el\u00edptica que conocemos, solo se admiten \"curvas con nombre\" o, si se admiten par\u00e1metros de curva expl\u00edcitos, especifican una codificaci\u00f3n X9.62 de curvas binarias (GF(2^m)) que no pueden representar valores de entrada problem\u00e1ticos. Por lo tanto, la probabilidad de existencia de una aplicaci\u00f3n vulnerable es baja. En particular, la codificaci\u00f3n X9.62 se utiliza para claves ECC en certificados X.509, por lo que no pueden ocurrir entradas problem\u00e1ticas en el contexto del procesamiento de certificados X.509. Cualquier caso de uso problem\u00e1tico tendr\u00eda que utilizar una codificaci\u00f3n de curva \"ex\u00f3tica\". Las API afectadas incluyen: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params() y varias funciones de soporte BN_GF2m_*(). Las aplicaciones que trabajan con par\u00e1metros de curva binarios expl\u00edcitos \"ex\u00f3ticos\" (GF(2^m)), que permiten representar polinomios de campo no v\u00e1lidos con un t\u00e9rmino constante cero, a trav\u00e9s de las API anteriores o similares, pueden terminar abruptamente como resultado de la lectura o escritura fuera de los l\u00edmites de la matriz. La ejecuci\u00f3n remota de c\u00f3digo no se puede descartar f\u00e1cilmente. Los m\u00f3dulos FIPS en 3.3, 3.2, 3.1 y 3.0 no se ven afectados por este problema."}], "id": "CVE-2024-9143", "lastModified": "2025-11-03T23:17:33.460", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 4.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "NONE", "integrityImpact": "LOW", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N", "version": "3.1"}, "exploitabilityScore": 2.8, "impactScore": 1.4, "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "type": "Secondary"}]}, "published": "2024-10-16T17:15:18.130", "references": [{"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/72ae83ad214d2eef262461365a1975707f862712"}, {"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/bc7e04d7c8d509fb78fc0e285aa948fb0da04700"}, {"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/c0d3e4d32d2805f49bec30547f225bc4d092e1f4"}, {"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/fdf6723362ca51bd883295efe206cb5b1cfa5154"}, {"source": "openssl-security@openssl.org", "url": "https://github.openssl.org/openssl/extended-releases/commit/8efc0cbaa8ebba8e116f7b81a876a4123594d86a"}, {"source": "openssl-security@openssl.org", "url": "https://github.openssl.org/openssl/extended-releases/commit/9d576994cec2b7aa37a91740ea7e680810957e41"}, {"source": "openssl-security@openssl.org", "url": "https://openssl-library.org/news/secadv/20241016.txt"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "url": "http://www.openwall.com/lists/oss-security/2024/10/16/1"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "url": "http://www.openwall.com/lists/oss-security/2024/10/23/1"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "url": "http://www.openwall.com/lists/oss-security/2024/10/24/1"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "url": "https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "url": "https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "url": "https://security.netapp.com/advisory/ntap-20241101-0001/"}], "sourceIdentifier": "openssl-security@openssl.org", "vulnStatus": "Awaiting Analysis", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-125"}, {"lang": "en", "value": "CWE-787"}], "source": "openssl-security@openssl.org", "type": "Secondary"}]}

{"bugzilla": {"description": "openssl: Low-level invalid GF(2^m) parameters lead to OOB memory access", "id": "2319236", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2319236"}, "csaw": false, "cvss3": {"cvss3_base_score": "3.7", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L", "status": "draft"}, "cwe": "CWE-787", "details": ["Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted\nexplicit values for the field polynomial can lead to out-of-bounds memory reads\nor writes.\nImpact summary: Out of bound memory writes can lead to an application crash or\neven a possibility of a remote code execution, however, in all the protocols\ninvolving Elliptic Curve Cryptography that we're aware of, either only \"named\ncurves\" are supported, or, if explicit curve parameters are supported, they\nspecify an X9.62 encoding of binary (GF(2^m)) curves that can't represent\nproblematic input values. Thus the likelihood of existence of a vulnerable\napplication is low.\nIn particular, the X9.62 encoding is used for ECC keys in X.509 certificates,\nso problematic inputs cannot occur in the context of processing X.509\ncertificates. Any problematic use-cases would have to be using an \"exotic\"\ncurve encoding.\nThe affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),\nand various supporting BN_GF2m_*() functions.\nApplications working with \"exotic\" explicit binary (GF(2^m)) curve parameters,\nthat make it possible to represent invalid field polynomials with a zero\nconstant term, via the above or similar APIs, may terminate abruptly as a\nresult of reading or writing outside of array bounds. Remote code execution\ncannot easily be ruled out.\nThe FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.", "A flaw was found in OpenSSL. 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. 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.\nApplications working with \"exotic\" explicit binary (GF(2^m)) curve parameters make it possible to represent invalid field polynomials with a zero constant term via the affected APIs (EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(),\nand various supporting BN_GF2m_*() functions) may terminate abruptly as a result of reading or writing outside of array bounds."], "name": "CVE-2024-9143", "package_state": [{"cpe": "cpe:/a:redhat:logging:5", "fix_state": "Fix deferred", "package_name": "openshift-logging/fluentd-rhel8", "product_name": "Logging Subsystem for Red Hat OpenShift"}, {"cpe": "cpe:/a:redhat:red_hat_3scale_amp:2", "fix_state": "Fix deferred", "package_name": "3scale-amp-backend-container", "product_name": "Red Hat 3scale API Management Platform 2"}, {"cpe": "cpe:/o:redhat:enterprise_linux:10", "fix_state": "Fix deferred", "package_name": "edk2", "product_name": "Red Hat Enterprise Linux 10"}, {"cpe": "cpe:/o:redhat:enterprise_linux:10", "fix_state": "Not affected", "package_name": "openssl", "product_name": "Red Hat Enterprise Linux 10"}, {"cpe": "cpe:/o:redhat:enterprise_linux:10", "fix_state": "Fix deferred", "package_name": "shim", "product_name": "Red Hat Enterprise Linux 10"}, {"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Out of support scope", "package_name": "openssl", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "openssl", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Fix deferred", "package_name": "ovmf", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "compat-openssl10", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Fix deferred", "package_name": "edk2", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Fix deferred", "package_name": "mingw-openssl", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "openssl", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Fix deferred", "package_name": "shim", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Fix deferred", "package_name": "shim-unsigned-x64", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "compat-openssl11", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Fix deferred", "package_name": "edk2", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "openssl", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Fix deferred", "package_name": "shim", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Fix deferred", "package_name": "shim-unsigned-aarch64", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Fix deferred", "package_name": "shim-unsigned-x64", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/a:redhat:jboss_core_services:1", "fix_state": "Fix deferred", "package_name": "openssl", "product_name": "Red Hat JBoss Core Services"}], "public_date": "2024-10-16T17:09:23Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2024-9143\nhttps://nvd.nist.gov/vuln/detail/CVE-2024-9143\nhttps://github.com/openssl/openssl/commit/72ae83ad214d2eef262461365a1975707f862712\nhttps://github.com/openssl/openssl/commit/bc7e04d7c8d509fb78fc0e285aa948fb0da04700\nhttps://github.com/openssl/openssl/commit/c0d3e4d32d2805f49bec30547f225bc4d092e1f4\nhttps://github.com/openssl/openssl/commit/fdf6723362ca51bd883295efe206cb5b1cfa5154\nhttps://github.openssl.org/openssl/extended-releases/commit/8efc0cbaa8ebba8e116f7b81a876a4123594d86a\nhttps://github.openssl.org/openssl/extended-releases/commit/9d576994cec2b7aa37a91740ea7e680810957e41\nhttps://openssl-library.org/news/secadv/20241016.txt"], "statement": "Openssl, compat-openssl10, and compat-openssl11 in Red Hat Enterprise Linux 7, 8, 9 are unaffected by this flaw, because the vulnerability is in code for binary field elliptic curves, which RHEL has never enabled.", "threat_severity": "Low"}

{"created": "2025-07-13T21:07:34.437665+00:00", "updated": "2025-07-13T21:07:34.437721+00:00", "vendors": ["openssl", "openssl$PRODUCT$openssl"]}