{"answers":{"affected":"3 open source packages ship an affected version, including libsecp256k1-rs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20399 in the wild and no public exploit code.","fix":"Upgrade libsecp256k1-rs to 0.3.1 or later.","what":"CVE-2019-20399 is a medium-severity vulnerability in n/a, published on 22 Jan 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-20399 and fix it if it is affected.\n\nWhat it is: CVE-2019-20399 is a medium-severity vulnerability in n/a, published on 22 Jan 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-20399 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- libsecp256k1-rs (crates.io): affected all versions; fixed in 0.3.1\n- libsecp256k1-rs (crates.io): affected all versions; fixed in 0.3.1\n- libsecp256k1-rs (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-20399/ (Markdown: https://insights.sbomify.com/CVE-2019-20399/index.md)","id":"CVE-2019-20399","markdown":"https://insights.sbomify.com/CVE-2019-20399/index.md","name":"CVE-2019-20399","record":{"aliases":["GHSA-7cqg-8449-rmfv","RUSTSEC-2020-0156"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust secp256k1 library","requires_auth":"none","summary":"A timing side-channel in the Parity libsecp256k1-rs library allows attackers to leak sensitive information via overflow checks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libsecp256k1","vendor":"parity"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.","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":"Observable Discrepancy in libsecp256k1-rs","id":"CVE-2019-20399","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":"Code injection in Jira Server","id":"CVE-2019-20400"},"packages":[{"ecosystem":"crates.io","fixed":["0.3.1"],"introduced":["0"],"last_affected":[],"package":"libsecp256k1-rs","purl":null,"source":"GHSA-7cqg-8449-rmfv"},{"ecosystem":"crates.io","fixed":["0.3.1"],"introduced":["0"],"last_affected":[],"package":"libsecp256k1-rs","purl":"pkg:cargo/libsecp256k1-rs","source":"GHSA-7cqg-8449-rmfv"},{"ecosystem":"crates.io","fixed":["0.3.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"libsecp256k1-rs","purl":"pkg:cargo/libsecp256k1-rs","source":"RUSTSEC-2020-0156"}],"prev":{"headline":"Null dereference in n/a","id":"CVE-2019-20398"},"products":["n/a"],"published":"2020-01-22","related":[{"cvss_score":9.8,"headline":"Overflow in libsecp256k1","id":"CVE-2021-38195","kev_date_added":null,"published":"2021-08-08"},{"cvss_score":7.5,"headline":"libsecp256k1 contains side-channel timing attack","id":"CVE-2019-25003","kev_date_added":null,"published":"2020-12-31"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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":"A timing side-channel in the Parity libsecp256k1-rs library allows attackers to leak sensitive information via overflow checks.","url":"https://insights.sbomify.com/CVE-2019-20399/"}