{"answers":{"affected":"3 open source packages ship an affected version, including cache. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-25903 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-25903 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-25903 is a high-severity vulnerability in n/a, published on 22 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-25903 and fix it if it is affected.\n\nWhat it is: CVE-2021-25903 is a high-severity vulnerability in n/a, published on 22 Jan 2021. 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-2021-25903 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- cache (crates.io): affected all versions up to 0.1.0; no fix listed\n- cache (crates.io): affected all versions up to 0.1.0; no fix listed\n- cache (crates.io): affected from 0.0.0-0; no fix listed\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-2021-25903/ (Markdown: https://insights.sbomify.com/CVE-2021-25903/index.md)","id":"CVE-2021-25903","markdown":"https://insights.sbomify.com/CVE-2021-25903/index.md","name":"CVE-2021-25903","record":{"aliases":["GHSA-gh87-6jr3-8q47","RUSTSEC-2021-0006"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust cache library","requires_auth":"none","summary":"A null pointer dereference in the Rust cache crate can cause a denial of service, requiring developers to upgrade the library.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cache","vendor":"cache_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"An issue was discovered in the cache crate through 2021-01-01 for Rust. A raw pointer is dereferenced.","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":false,"headline":"Null pointer deference in cache","id":"CVE-2021-25903","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"null_dereference","year":"2021"},"n_packages":3,"n_references":1,"next":{"headline":"Null pointer deference in av-data","id":"CVE-2021-25904"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.1.0"],"package":"cache","purl":null,"source":"GHSA-gh87-6jr3-8q47"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.1.0"],"package":"cache","purl":"pkg:cargo/cache","source":"GHSA-gh87-6jr3-8q47"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"cache","purl":"pkg:cargo/cache","source":"RUSTSEC-2021-0006"}],"prev":{"headline":"Double free in glsl-layout","id":"CVE-2021-25902"},"products":["n/a"],"published":"2021-01-22","related":[{"cvss_score":8.1,"headline":"Data races in cache","id":"CVE-2020-36448","kev_date_added":null,"published":"2021-08-08"}],"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-03","vendors":["n/a"]},"summary":"A null pointer dereference in the Rust cache crate can cause a denial of service, requiring developers to upgrade the library.","url":"https://insights.sbomify.com/CVE-2021-25903/"}