{"answers":{"affected":"3 open source packages ship an affected version, including lazy-init. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-25901 in the wild and no public exploit code.","fix":"Upgrade lazy-init to a fixed version for your release line: 0.4.0 or 0.4.1-0.","what":"CVE-2021-25901 is a medium-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-25901 and fix it if it is affected.\n\nWhat it is: CVE-2021-25901 is a medium-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-25901 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- lazy-init (crates.io): affected all versions; fixed in 0.4.0\n- lazy-init (crates.io): affected all versions; fixed in 0.4.0\n- lazy-init (crates.io): affected from 0.0.0-0; fixed in 0.4.1-0\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-25901/ (Markdown: https://insights.sbomify.com/CVE-2021-25901/index.md)","id":"CVE-2021-25901","markdown":"https://insights.sbomify.com/CVE-2021-25901/index.md","name":"CVE-2021-25901","record":{"aliases":["GHSA-w47j-hqpf-qw9w","RUSTSEC-2021-0004"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust lazy-init crate","requires_auth":"none","summary":"A missing Send bound in the lazy-init crate allows data races, potentially leading to memory corruption or crashes in Rust applications.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lazy-init","vendor":"lazy-init_project"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"An issue was discovered in the lazy-init crate through 2021-01-17 for Rust. Lazy lacks a Send bound, leading to a data race.","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":"Out of bounds read in lazy-init","id":"CVE-2021-25901","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"race_condition","year":"2021"},"n_packages":3,"n_references":1,"next":{"headline":"Double free in glsl-layout","id":"CVE-2021-25902"},"packages":[{"ecosystem":"crates.io","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"lazy-init","purl":null,"source":"GHSA-w47j-hqpf-qw9w"},{"ecosystem":"crates.io","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"lazy-init","purl":"pkg:cargo/lazy-init","source":"GHSA-w47j-hqpf-qw9w"},{"ecosystem":"crates.io","fixed":["0.4.1-0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"lazy-init","purl":"pkg:cargo/lazy-init","source":"RUSTSEC-2021-0004"}],"prev":{"headline":"Buffer overflow in SmallVec::insert_many","id":"CVE-2021-25900"},"products":["n/a"],"published":"2021-01-22","related":[],"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 missing Send bound in the lazy-init crate allows data races, potentially leading to memory corruption or crashes in Rust applications.","url":"https://insights.sbomify.com/CVE-2021-25901/"}