{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36318 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-36318 is a critical use after free vulnerability in n/a, published on 11 Apr 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-2020-36318 and fix it if it is affected.\n\nWhat it is: CVE-2020-36318 is a critical use after free vulnerability in n/a, published on 11 Apr 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-2020-36318 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2020-36318/ (Markdown: https://insights.sbomify.com/CVE-2020-36318/index.md)","id":"CVE-2020-36318","markdown":"https://insights.sbomify.com/CVE-2020-36318/index.md","name":"CVE-2020-36318","record":{"aliases":["DEBIAN-CVE-2020-36318","GHSA-w7c8-v5h2-32ff","UBUNTU-CVE-2020-36318"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust standard library","requires_auth":"none","summary":"A bug in Rust's VecDeque::make_contiguous can cause use-after-free or double free, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rust","vendor":"rust-lang"}],"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":[{"id":"CWE-416","name":"Use After Free"},{"id":"CWE-415","name":"Double Free"}],"description":"In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.","ecosystems":[],"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":"Use after free in n/a","id":"CVE-2020-36318","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Potential sensitive data exposure in applications using Vaadin 15","id":"CVE-2020-36319"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-36317"},"products":["n/a"],"published":"2021-04-11","related":[{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2018-1000810","kev_date_added":null,"published":"2018-10-08"},{"cvss_score":9.1,"headline":"Security feature bypass in n/a","id":"CVE-2021-29922","kev_date_added":null,"published":"2021-08-07"},{"cvss_score":8.2,"headline":"Rust OS Command Injection/Argument Injection vulnerability","id":"CVE-2024-43402","kev_date_added":null,"published":"2024-09-04"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2018-1000657","kev_date_added":null,"published":"2018-08-20"},{"cvss_score":7.8,"headline":"Other in n/a","id":"CVE-2018-1000622","kev_date_added":null,"published":"2018-07-09"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2015-20001","kev_date_added":null,"published":"2021-04-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-04","vendors":["n/a"]},"summary":"A bug in Rust's VecDeque::make_contiguous can cause use-after-free or double free, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2020-36318/"}