{"answers":{"affected":"3 open source packages ship an affected version, including sodiumoxide. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-25002 in the wild and no public exploit code.","fix":"Upgrade sodiumoxide to 0.2.5 or later.","what":"CVE-2019-25002 is a critical 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-25002 and fix it if it is affected.\n\nWhat it is: CVE-2019-25002 is a critical 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-25002 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sodiumoxide (crates.io): affected from 0.0.0-0; fixed in 0.2.5\n- sodiumoxide (crates.io): affected from 0.2.0; fixed in 0.2.5\n- sodiumoxide (crates.io): affected from 0.2.0; fixed in 0.2.5\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-25002/ (Markdown: https://insights.sbomify.com/CVE-2019-25002/index.md)","id":"CVE-2019-25002","markdown":"https://insights.sbomify.com/CVE-2019-25002/index.md","name":"CVE-2019-25002","record":{"aliases":["GHSA-wrvc-72w7-xpmj","RUSTSEC-2019-0026"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust crypto library","requires_auth":"none","summary":"A logic error in the sodiumoxide Rust crate causes hash comparisons to always return true, bypassing integrity checks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sodiumoxide","vendor":"sodiumoxide_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in the sodiumoxide crate before 0.2.5 for Rust. generichash::Digest::eq compares itself to itself and thus has degenerate security properties.","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":"Incorrect Comparison in sodiumoxide","id":"CVE-2019-25002","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":3,"n_references":1,"next":{"headline":"libsecp256k1 contains side-channel timing attack","id":"CVE-2019-25003"},"packages":[{"ecosystem":"crates.io","fixed":["0.2.5"],"introduced":["0.0.0-0"],"last_affected":[],"package":"sodiumoxide","purl":"pkg:cargo/sodiumoxide","source":"RUSTSEC-2019-0026"},{"ecosystem":"crates.io","fixed":["0.2.5"],"introduced":["0.2.0"],"last_affected":[],"package":"sodiumoxide","purl":null,"source":"GHSA-wrvc-72w7-xpmj"},{"ecosystem":"crates.io","fixed":["0.2.5"],"introduced":["0.2.0"],"last_affected":[],"package":"sodiumoxide","purl":"pkg:cargo/sodiumoxide","source":"GHSA-wrvc-72w7-xpmj"}],"prev":{"headline":"Out of bounds write in serde_cbor","id":"CVE-2019-25001"},"products":["n/a"],"published":"2020-12-31","related":[{"cvss_score":6.5,"headline":"scalarmult() vulnerable to degenerate public keys","id":"CVE-2017-1000168","kev_date_added":null,"published":"2017-11-17"}],"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":"A logic error in the sodiumoxide Rust crate causes hash comparisons to always return true, bypassing integrity checks.","url":"https://insights.sbomify.com/CVE-2019-25002/"}