{"answers":{"affected":"5 open source packages ship an affected version, including nanorand. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-45705 in the wild and no public exploit code.","fix":"Upgrade nanorand to 0.6.1 or later.","what":"CVE-2021-45705 is a critical memory corruption vulnerability in n/a, published on 26 Dec 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-45705 and fix it if it is affected.\n\nWhat it is: CVE-2021-45705 is a critical memory corruption vulnerability in n/a, published on 26 Dec 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-45705 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nanorand (crates.io): affected from 0.5.0; fixed in 0.6.1\n- nanorand (crates.io): affected from 0.5.0; fixed in 0.6.1\n- nanorand (crates.io): affected from 0.5.0; fixed in 0.6.1\n- nanorand (crates.io): affected from 0.5.0; fixed in 0.6.1\n- nanorand (crates.io): affected from 0.5.0; fixed in 0.6.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-2021-45705/ (Markdown: https://insights.sbomify.com/CVE-2021-45705/index.md)","id":"CVE-2021-45705","markdown":"https://insights.sbomify.com/CVE-2021-45705/index.md","name":"CVE-2021-45705","record":{"aliases":["GHSA-p6gj-gpc8-f8xw","GHSA-r57r-j98g-587f","RUSTSEC-2021-0114"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust random number library","requires_auth":"none","summary":"The nanorand Rust library allows multiple mutable references to the same object, potentially leading to memory corruption and undefined behavior.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nanorand","vendor":"nanorand_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 nanorand crate before 0.6.1 for Rust. There can be multiple mutable references to the same object because the TlsWyRand Deref implementation dereferences a raw pointer.","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":"Aliased mutable references from `tls_rand` \u0026 `TlsWyRand`","id":"CVE-2021-45705","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":5,"n_references":2,"next":{"headline":"Memory flaw in zeroize_derive","id":"CVE-2021-45706"},"packages":[{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0.5.0"],"last_affected":[],"package":"nanorand","purl":null,"source":"GHSA-p6gj-gpc8-f8xw"},{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0.5.0"],"last_affected":[],"package":"nanorand","purl":"pkg:cargo/nanorand","source":"GHSA-p6gj-gpc8-f8xw"},{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0.5.0"],"last_affected":[],"package":"nanorand","purl":null,"source":"GHSA-r57r-j98g-587f"},{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0.5.0"],"last_affected":[],"package":"nanorand","purl":"pkg:cargo/nanorand","source":"GHSA-r57r-j98g-587f"},{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0.5.0"],"last_affected":[],"package":"nanorand","purl":"pkg:cargo/nanorand","source":"RUSTSEC-2021-0114"}],"prev":{"headline":"AtomicBucket\u003cT\u003e unconditionally implements Send/Sync","id":"CVE-2021-45704"},"products":["n/a"],"published":"2021-12-26","related":[{"cvss_score":9.8,"headline":"Improper random number generation in nanorand","id":"CVE-2020-35926","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"The nanorand Rust library allows multiple mutable references to the same object, potentially leading to memory corruption and undefined behavior.","url":"https://insights.sbomify.com/CVE-2021-45705/"}