{"answers":{"affected":"3 open source packages ship an affected version, including crayon. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35889 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35889 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35889 is a high-severity vulnerability in n/a, published on 31 Dec 2020. 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-35889 and fix it if it is affected.\n\nWhat it is: CVE-2020-35889 is a high-severity vulnerability in n/a, published on 31 Dec 2020. 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-35889 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- crayon (crates.io): affected all versions up to 0.7.1; no fix listed\n- crayon (crates.io): affected all versions up to 0.7.1; no fix listed\n- crayon (crates.io): affected from 0.0.0-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-35889/ (Markdown: https://insights.sbomify.com/CVE-2020-35889/index.md)","id":"CVE-2020-35889","markdown":"https://insights.sbomify.com/CVE-2020-35889/index.md","name":"CVE-2020-35889","record":{"aliases":["GHSA-m833-jv95-mfjh","RUSTSEC-2020-0037"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust crayon crate","requires_auth":"none","summary":"A time-of-check time-of-use race condition in the crayon crate can lead to memory safety violations and potential code execution.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"crayon","vendor":"crayon_project"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"An issue was discovered in the crayon crate through 2020-08-31 for Rust. A TOCTOU issue has a resultant memory safety violation via HandleLike.","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":"Memory safety violation in crayon","id":"CVE-2020-35889","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"race_condition","year":"2020"},"n_packages":3,"n_references":1,"next":{"headline":"Out of bounds read in ordnung","id":"CVE-2020-35890"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.7.1"],"package":"crayon","purl":null,"source":"GHSA-m833-jv95-mfjh"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.7.1"],"package":"crayon","purl":"pkg:cargo/crayon","source":"GHSA-m833-jv95-mfjh"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"crayon","purl":"pkg:cargo/crayon","source":"RUSTSEC-2020-0037"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-35888"},"products":["n/a"],"published":"2020-12-31","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-04","vendors":["n/a"]},"summary":"A time-of-check time-of-use race condition in the crayon crate can lead to memory safety violations and potential code execution.","url":"https://insights.sbomify.com/CVE-2020-35889/"}