{"answers":{"affected":"3 open source packages ship an affected version, including ws. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35896 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35896 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35896 is a high-severity denial of service 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-35896 and fix it if it is affected.\n\nWhat it is: CVE-2020-35896 is a high-severity denial of service 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-35896 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ws (crates.io): affected all versions up to 0.9.1; no fix listed\n- ws (crates.io): affected all versions up to 0.9.1; no fix listed\n- ws (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-35896/ (Markdown: https://insights.sbomify.com/CVE-2020-35896/index.md)","id":"CVE-2020-35896","markdown":"https://insights.sbomify.com/CVE-2020-35896/index.md","name":"CVE-2020-35896","record":{"aliases":["GHSA-rh7x-ppxx-p34c","RUSTSEC-2020-0043"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust WebSocket library","requires_auth":"none","summary":"Attackers can cause remote memory exhaustion in applications using the ws crate due to unbounded outgoing buffers, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ws-rs","vendor":"ws-rs_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"An issue was discovered in the ws crate through 2020-09-25 for Rust. The outgoing buffer is not properly limited, leading to a remote memory-consumption attack.","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":"Insufficient size checks in ws","id":"CVE-2020-35896","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2020"},"n_packages":3,"n_references":1,"next":{"headline":"Data races in atom","id":"CVE-2020-35897"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.9.1"],"package":"ws","purl":null,"source":"GHSA-rh7x-ppxx-p34c"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.9.1"],"package":"ws","purl":"pkg:cargo/ws","source":"GHSA-rh7x-ppxx-p34c"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"ws","purl":"pkg:cargo/ws","source":"RUSTSEC-2020-0043"}],"prev":{"headline":"Out-of-bounds write in stack","id":"CVE-2020-35895"},"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":"Attackers can cause remote memory exhaustion in applications using the ws crate due to unbounded outgoing buffers, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2020-35896/"}