{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35904 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-35904 is a medium-severity vulnerability in n/a, published on 31 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-35904 and fix it if it is affected.\n\nWhat it is: CVE-2020-35904 is a medium-severity vulnerability in n/a, published on 31 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-35904 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-35904/ (Markdown: https://insights.sbomify.com/CVE-2020-35904/index.md)","id":"CVE-2020-35904","markdown":"https://insights.sbomify.com/CVE-2020-35904/index.md","name":"CVE-2020-35904","record":{"aliases":["DEBIAN-CVE-2020-35904","UBUNTU-CVE-2020-35904"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust crossbeam-channel crate","requires_auth":"low_privilege","summary":"Incorrect memory allocation expectations in the crossbeam-channel crate may lead to undefined behavior or crashes during iteration.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"crossbeam-channel","vendor":"crossbeam-channel_project"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in the crossbeam-channel crate before 0.4.4 for Rust. It has incorrect expectations about the relationship between the memory allocation and how many iterator elements there are.","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":"Other in n/a","id":"CVE-2020-35904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"MutexGuard::map can cause a data race in safe code","id":"CVE-2020-35905"},"packages":[],"prev":{"headline":"Out of bounds read in dync","id":"CVE-2020-35903"},"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":"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":"Incorrect memory allocation expectations in the crossbeam-channel crate may lead to undefined behavior or crashes during iteration.","url":"https://insights.sbomify.com/CVE-2020-35904/"}