{"answers":{"affected":"2 open source packages ship an affected version, including cgc. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36468 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36468 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36468 is a medium-severity vulnerability in n/a, published on 8 Aug 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-36468 and fix it if it is affected.\n\nWhat it is: CVE-2020-36468 is a medium-severity vulnerability in n/a, published on 8 Aug 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-36468 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- cgc (crates.io): affected all versions up to 0.4.0; no fix listed\n- cgc (crates.io): affected all versions up to 0.4.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-2020-36468/ (Markdown: https://insights.sbomify.com/CVE-2020-36468/index.md)","id":"CVE-2020-36468","markdown":"https://insights.sbomify.com/CVE-2020-36468/index.md","name":"CVE-2020-36468","record":{"aliases":["GHSA-pwhf-7427-9vv2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust cgc crate","requires_auth":"none","summary":"Non-atomic pointer writes in the Rust cgc crate can lead to race conditions, potentially causing memory corruption or crashes.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cgc","vendor":"cgc_project"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in the cgc crate through 2020-12-10 for Rust. Ptr::write performs non-atomic write operations on an underlying 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":false,"headline":"Non-atomic writes in cgc","id":"CVE-2020-36468","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"race_condition","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Data races in appendix","id":"CVE-2020-36469"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.4.0"],"package":"cgc","purl":null,"source":"GHSA-pwhf-7427-9vv2"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.4.0"],"package":"cgc","purl":"pkg:cargo/cgc","source":"GHSA-pwhf-7427-9vv2"}],"prev":{"headline":"Multiple soundness issues in cgc","id":"CVE-2020-36467"},"products":["n/a"],"published":"2021-08-08","related":[{"cvss_score":5.9,"headline":"Data races in cgc","id":"CVE-2020-36466","kev_date_added":null,"published":"2021-08-08"},{"cvss_score":5.9,"headline":"Multiple soundness issues in cgc","id":"CVE-2020-36467","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":"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":"Non-atomic pointer writes in the Rust cgc crate can lead to race conditions, potentially causing memory corruption or crashes.","url":"https://insights.sbomify.com/CVE-2020-36468/"}