{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-9231 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-9231 is a medium-severity vulnerability in OpenSSL, published on 30 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-9231 and fix it if it is affected.\n\nWhat it is: CVE-2025-9231 is a medium-severity vulnerability in OpenSSL, published on 30 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-9231 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-2025-9231/ (Markdown: https://insights.sbomify.com/CVE-2025-9231/index.md)","id":"CVE-2025-9231","markdown":"https://insights.sbomify.com/CVE-2025-9231/index.md","name":"CVE-2025-9231","record":{"aliases":["ALPINE-CVE-2025-9231","BELL-CVE-2025-9231","DEBIAN-CVE-2025-9231","ECHO-2b7e-78d4-c817","GHSA-9mrx-mqmg-gwj9","JLSEC-2026-267","MINI-4x56-859r-prjq","MINI-f394-p673-w5hp","UBUNTU-CVE-2025-9231"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenSSL cryptographic library","requires_auth":"none","summary":"A timing side-channel in OpenSSL's SM2 implementation on 64-bit ARM may allow attackers to recover private keys via remote timing measurements.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"openssl","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-385","name":"Covert Timing Channel"}],"description":"Issue summary: A timing side-channel which could potentially allow remote\nrecovery of the private key exists in the SM2 algorithm implementation on 64 bit\nARM platforms.\n\nImpact summary: A timing side-channel in SM2 signature computations on 64 bit\nARM platforms could allow recovering the private key by an attacker..\n\nWhile remote key recovery over a network was not attempted by the reporter,\ntiming measurements revealed a timing signal which may allow such an attack.\n\nOpenSSL does not directly support certificates with SM2 keys in TLS, and so\nthis CVE is not relevant in most TLS contexts.  However, given that it is\npossible to add support for such certificates via a custom provider, coupled\nwith the fact that in such a custom provider context the private key may be\nrecoverable via remote timing measurements, we consider this to be a Moderate\nseverity issue.\n\nThe FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this\nissue, as SM2 is not an approved algorithm.","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":"Timing side-channel in SM2 algorithm on 64 bit ARM","id":"CVE-2025-9231","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"Out-of-bounds read in HTTP client no_proxy handling","id":"CVE-2025-9232"},"packages":[],"prev":{"headline":"Out-of-bounds read \u0026 write in RFC 3211 KEK Unwrap","id":"CVE-2025-9230"},"products":["OpenSSL"],"published":"2025-09-30","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-07-14","vendors":["OpenSSL"]},"summary":"A timing side-channel in OpenSSL's SM2 implementation on 64-bit ARM may allow attackers to recover private keys via remote timing measurements.","url":"https://insights.sbomify.com/CVE-2025-9231/"}