{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-9143 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-9143 is a medium-severity memory corruption vulnerability in OpenSSL, published on 16 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-9143 and fix it if it is affected.\n\nWhat it is: CVE-2024-9143 is a medium-severity memory corruption vulnerability in OpenSSL, published on 16 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-9143 in the wild and no public exploit code.\n\nAffected product: OpenSSL. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-9143/ (Markdown: https://insights.sbomify.com/CVE-2024-9143/index.md)","id":"CVE-2024-9143","markdown":"https://insights.sbomify.com/CVE-2024-9143/index.md","name":"CVE-2024-9143","record":{"aliases":["ALPINE-CVE-2024-9143","AZL-78531","BELL-CVE-2024-9143","CLEANSTART-2026-QL44288","DEBIAN-CVE-2024-9143","GHSA-q764-r57m-9wp9","JLSEC-2026-254","MGASA-2024-0354","MGASA-2024-0355","MINI-xxrx-crr8-74g3","OESA-2024-2384","OESA-2024-2385","OESA-2024-2386","OESA-2024-2387","OESA-2024-2480","OESA-2025-1352","UBUNTU-CVE-2024-9143"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenSSL cryptographic library","requires_auth":"low_privilege","summary":"Attackers can trigger out-of-bounds memory access in OpenSSL when using low-level APIs with invalid GF(2^m) curve parameters, potentially causing crashes or remote code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"openssl","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Low-level invalid GF(2^m) parameters lead to OOB memory access","id":"CVE-2024-9143","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":7,"next":{"headline":"Local command injection in Wiz Code Visual Studio Code extension","id":"CVE-2024-9145"},"packages":[],"prev":{"headline":"Local File Inclusion (LFI) in Olgu Computer Systems' e-Belediye","id":"CVE-2024-9142"},"products":["OpenSSL"],"published":"2024-10-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["OpenSSL"]},"summary":"Attackers can trigger out-of-bounds memory access in OpenSSL when using low-level APIs with invalid GF(2^m) curve parameters, potentially causing crashes or remote code execution.","url":"https://insights.sbomify.com/CVE-2024-9143/"}