{"answers":{"affected":"3 open source packages ship an affected version, including safe-transmute. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-21000 in the wild and no public exploit code.","fix":"Upgrade safe-transmute to 0.10.1 or later.","what":"CVE-2018-21000 is a critical memory corruption vulnerability in n/a, published on 26 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-21000 and fix it if it is affected.\n\nWhat it is: CVE-2018-21000 is a critical memory corruption vulnerability in n/a, published on 26 Aug 2019. 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-2018-21000 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- safe-transmute (crates.io): affected from 0.4.0; fixed in 0.10.1\n- safe-transmute (crates.io): affected from 0.4.0; fixed in 0.10.1\n- safe-transmute (crates.io): affected from 0.4.0; fixed in 0.10.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-2018-21000/ (Markdown: https://insights.sbomify.com/CVE-2018-21000/index.md)","id":"CVE-2018-21000","markdown":"https://insights.sbomify.com/CVE-2018-21000/index.md","name":"CVE-2018-21000","record":{"aliases":["GHSA-2v78-j59h-fmpf","RUSTSEC-2018-0013","UBUNTU-CVE-2018-21000"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust safe-transmute crate","requires_auth":"none","summary":"Heap memory corruption in the safe-transmute crate allows attackers to potentially execute arbitrary code or cause denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"safe-transmute","vendor":"safe-transmute_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An issue was discovered in the safe-transmute crate before 0.10.1 for Rust. A constructor's arguments are in the wrong order, causing heap memory corruption.","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":"Heap overflow or corruption in safe-transmute","id":"CVE-2018-21000","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":3,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-21001"},"packages":[{"ecosystem":"crates.io","fixed":["0.10.1"],"introduced":["0.4.0"],"last_affected":[],"package":"safe-transmute","purl":null,"source":"GHSA-2v78-j59h-fmpf"},{"ecosystem":"crates.io","fixed":["0.10.1"],"introduced":["0.4.0"],"last_affected":[],"package":"safe-transmute","purl":"pkg:cargo/safe-transmute","source":"GHSA-2v78-j59h-fmpf"},{"ecosystem":"crates.io","fixed":["0.10.1"],"introduced":["0.4.0"],"last_affected":[],"package":"safe-transmute","purl":"pkg:cargo/safe-transmute","source":"RUSTSEC-2018-0013"}],"prev":{"headline":"Flaw in streaming state in orion","id":"CVE-2018-20999"},"products":["n/a"],"published":"2019-08-26","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-05","vendors":["n/a"]},"summary":"Heap memory corruption in the safe-transmute crate allows attackers to potentially execute arbitrary code or cause denial of service.","url":"https://insights.sbomify.com/CVE-2018-21000/"}