{"answers":{"affected":"3 open source packages ship an affected version, including libsecp256k1. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-25003 in the wild and no public exploit code.","fix":"Upgrade libsecp256k1 to 0.3.1 or later.","what":"CVE-2019-25003 is a high-severity vulnerability in n/a, published on 31 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-25003 and fix it if it is affected.\n\nWhat it is: CVE-2019-25003 is a high-severity vulnerability in n/a, published on 31 Dec 2020. 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-2019-25003 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- libsecp256k1 (crates.io): affected all versions; fixed in 0.3.1\n- libsecp256k1 (crates.io): affected all versions; fixed in 0.3.1\n- libsecp256k1 (crates.io): affected from 0.0.0-0; fixed in 0.3.1\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-2019-25003/ (Markdown: https://insights.sbomify.com/CVE-2019-25003/index.md)","id":"CVE-2019-25003","markdown":"https://insights.sbomify.com/CVE-2019-25003/index.md","name":"CVE-2019-25003","record":{"aliases":["GHSA-hrjm-c879-pp86","RUSTSEC-2019-0027"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust crypto library","requires_auth":"none","summary":"Attackers can exploit a timing side-channel in the libsecp256k1 Rust crate to obtain sensitive cryptographic information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libsecp256k1","vendor":"parity"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"An issue was discovered in the libsecp256k1 crate before 0.3.1 for Rust. Scalar::check_overflow allows a timing side-channel attack; consequently, attackers can obtain sensitive information.","ecosystems":["crates.io"],"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":"libsecp256k1 contains side-channel timing attack","id":"CVE-2019-25003","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":3,"n_references":1,"next":{"headline":"Unsound casting in flatbuffers","id":"CVE-2019-25004"},"packages":[{"ecosystem":"crates.io","fixed":["0.3.1"],"introduced":["0"],"last_affected":[],"package":"libsecp256k1","purl":null,"source":"GHSA-hrjm-c879-pp86"},{"ecosystem":"crates.io","fixed":["0.3.1"],"introduced":["0"],"last_affected":[],"package":"libsecp256k1","purl":"pkg:cargo/libsecp256k1","source":"GHSA-hrjm-c879-pp86"},{"ecosystem":"crates.io","fixed":["0.3.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"libsecp256k1","purl":"pkg:cargo/libsecp256k1","source":"RUSTSEC-2019-0027"}],"prev":{"headline":"Incorrect Comparison in sodiumoxide","id":"CVE-2019-25002"},"products":["n/a"],"published":"2020-12-31","related":[{"cvss_score":9.8,"headline":"Overflow in libsecp256k1","id":"CVE-2021-38195","kev_date_added":null,"published":"2021-08-08"},{"cvss_score":5.9,"headline":"Observable Discrepancy in libsecp256k1-rs","id":"CVE-2019-20399","kev_date_added":null,"published":"2020-01-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can exploit a timing side-channel in the libsecp256k1 Rust crate to obtain sensitive cryptographic information.","url":"https://insights.sbomify.com/CVE-2019-25003/"}