{"answers":{"affected":"3 open source packages ship an affected version, including mio. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35922 in the wild and no public exploit code.","fix":"Upgrade mio to 0.7.6 or later.","what":"CVE-2020-35922 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-35922 and fix it if it is affected.\n\nWhat it is: CVE-2020-35922 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-35922 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mio (crates.io): affected from 0.7.0; fixed in 0.7.6\n- mio (crates.io): affected from 0.7.0; fixed in 0.7.6\n- mio (crates.io): affected from 0.7.0; fixed in 0.7.6\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-35922/ (Markdown: https://insights.sbomify.com/CVE-2020-35922/index.md)","id":"CVE-2020-35922","markdown":"https://insights.sbomify.com/CVE-2020-35922/index.md","name":"CVE-2020-35922","record":{"aliases":["GHSA-pf3p-x6qj-6j7q","RUSTSEC-2020-0081","UBUNTU-CVE-2020-35922"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust networking library","requires_auth":"low_privilege","summary":"The mio crate had incorrect assumptions about SocketAddr memory layout, potentially causing undefined behavior or crashes in Rust applications.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mio","vendor":"mio_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 mio crate before 0.7.6 for Rust. It has false expectations about the std::net::SocketAddr memory representation.","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":true,"headline":"mio invalidly assumes the memory layout of std::net::SocketAddr","id":"CVE-2020-35922","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2020"},"n_packages":3,"n_references":1,"next":{"headline":"ordered_float:NotNan may contain NaN after panic in assignment operators","id":"CVE-2020-35923"},"packages":[{"ecosystem":"crates.io","fixed":["0.7.6"],"introduced":["0.7.0"],"last_affected":[],"package":"mio","purl":null,"source":"GHSA-pf3p-x6qj-6j7q"},{"ecosystem":"crates.io","fixed":["0.7.6"],"introduced":["0.7.0"],"last_affected":[],"package":"mio","purl":"pkg:cargo/mio","source":"GHSA-pf3p-x6qj-6j7q"},{"ecosystem":"crates.io","fixed":["0.7.6"],"introduced":["0.7.0"],"last_affected":[],"package":"mio","purl":"pkg:cargo/mio","source":"RUSTSEC-2020-0081"}],"prev":{"headline":"miow invalidly assumes the memory layout of std::net::SocketAddr","id":"CVE-2020-35921"},"products":["n/a"],"published":"2020-12-31","related":[{"cvss_score":7.5,"headline":"Mio's tokens for named pipes may be delivered after deregistration","id":"CVE-2024-27308","kev_date_added":null,"published":"2024-03-06"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"The mio crate had incorrect assumptions about SocketAddr memory layout, potentially causing undefined behavior or crashes in Rust applications.","url":"https://insights.sbomify.com/CVE-2020-35922/"}