{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15254 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-15254 is a high-severity memory corruption vulnerability in crossbeam-rs crossbeam, published on 16 Oct 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-15254 and fix it if it is affected.\n\nWhat it is: CVE-2020-15254 is a high-severity memory corruption vulnerability in crossbeam-rs crossbeam, published on 16 Oct 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-15254 in the wild and no public exploit code.\n\nAffected product: crossbeam-rs crossbeam. 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-15254/ (Markdown: https://insights.sbomify.com/CVE-2020-15254/index.md)","id":"CVE-2020-15254","markdown":"https://insights.sbomify.com/CVE-2020-15254/index.md","name":"CVE-2020-15254","record":{"aliases":["UBUNTU-CVE-2020-15254"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust concurrency library","requires_auth":"none","summary":"An attacker can trigger memory corruption in the Crossbeam bounded channel due to incorrect capacity assumptions, potentially causing crashes or arbitrary code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"crossbeam","vendor":"crossbeam_project"}],"cvss":{"score":8.1,"severity":"high","source":"cna","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-401","name":"Missing Release of Memory after Effective Lifetime"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Crossbeam is a set of tools for concurrent programming. In crossbeam-channel before version 0.4.4, the bounded channel incorrectly assumes that `Vec::from_iter` has allocated capacity that same as the number of iterator elements. `Vec::from_iter` does not actually guarantee that and may allocate extra memory. The destructor of the `bounded` channel reconstructs `Vec` from the raw pointer based on the incorrect assumes described above. This is unsound and causing deallocation with the incorrect capacity when `Vec::from_iter` has allocated different sizes with the number of iterator elements. This has been fixed in crossbeam-channel 0.4.4.","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":"Undefined Behavior in bounded Crossbeam channel","id":"CVE-2020-15254","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"CSV injection in Anuko Time Tracker","id":"CVE-2020-15255"},"packages":[],"prev":{"headline":"Stored XSS in Grocy","id":"CVE-2020-15253"},"products":["crossbeam"],"published":"2020-10-16","related":[{"cvss_score":9.8,"headline":"Data race in crossbeam-deque","id":"CVE-2021-32810","kev_date_added":null,"published":"2021-08-02"},{"cvss_score":9.8,"headline":"Double free in crossbeam","id":"CVE-2018-20996","kev_date_added":null,"published":"2019-08-26"},{"cvss_score":8.1,"headline":"Improper Restriction of Operations within the Bounds of a Memory Buffer and Race Condition in crossbeam-utils","id":"CVE-2022-23639","kev_date_added":null,"published":"2022-02-15"}],"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":["crossbeam-rs"]},"summary":"An attacker can trigger memory corruption in the Crossbeam bounded channel due to incorrect capacity assumptions, potentially causing crashes or arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2020-15254/"}