{"answers":{"affected":"7 open source packages ship an affected version, including tokio.","exploited":"There is no known exploitation of GHSA-rr8g-9fpq-6wmg in the wild and no public exploit code.","fix":"Upgrade tokio to a fixed version for your release line: 1.38.2, 1.42.1, 1.43.1 or 1.44.2.","what":"GHSA-rr8g-9fpq-6wmg is a memory corruption vulnerability in tokio, published on 7 Apr 2025."},"fix_prompt":"Check this codebase for GHSA-rr8g-9fpq-6wmg and fix it if it is affected.\n\nWhat it is: GHSA-rr8g-9fpq-6wmg is a memory corruption vulnerability in tokio, published on 7 Apr 2025. \nExploitation: There is no known exploitation of GHSA-rr8g-9fpq-6wmg in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tokio (crates.io): affected from 0.2.5; fixed in 1.38.2, 1.42.1, 1.43.1, 1.44.2\n- tokio (crates.io): affected from 0.2.5; fixed in 1.38.2\n- tokio (crates.io): affected from 0.2.5; fixed in 1.38.2\n- tokio (crates.io): affected from 1.39.0; fixed in 1.43.1\n- tokio (crates.io): affected from 1.39.0; fixed in 1.43.1\n- tokio (crates.io): affected from 1.44.0; fixed in 1.44.2\n- tokio (crates.io): affected from 1.44.0; fixed in 1.44.2\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/GHSA-rr8g-9fpq-6wmg/ (Markdown: https://insights.sbomify.com/GHSA-rr8g-9fpq-6wmg/index.md)","id":"GHSA-rr8g-9fpq-6wmg","markdown":"https://insights.sbomify.com/GHSA-rr8g-9fpq-6wmg/index.md","name":"GHSA-rr8g-9fpq-6wmg","record":{"aliases":["RUSTSEC-2025-0023"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust broadcast channel","requires_auth":"none","summary":"Unsoundness in Rust broadcast channels allows memory corruption when cloning non-Sync values, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The broadcast channel internally calls `clone` on the stored value when receiving it, and only requires `T:Send`. This means that using the broadcast channel with values that are `Send` but not `Sync` can trigger unsoundness if the `clone` implementation makes use of the value being `!Sync`.\n\nThank you to Austin Bonander for finding and reporting this issue.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Tokio broadcast channel calls clone in parallel, but does not require `Sync`","id":"GHSA-rr8g-9fpq-6wmg","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":7,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["1.38.2","1.42.1","1.43.1","1.44.2"],"introduced":["0.2.5","1.39.0","1.43.0","1.44.0"],"last_affected":[],"package":"tokio","purl":"pkg:cargo/tokio","source":"RUSTSEC-2025-0023"},{"ecosystem":"crates.io","fixed":["1.38.2"],"introduced":["0.2.5"],"last_affected":[],"package":"tokio","purl":null,"source":"GHSA-rr8g-9fpq-6wmg"},{"ecosystem":"crates.io","fixed":["1.38.2"],"introduced":["0.2.5"],"last_affected":[],"package":"tokio","purl":"pkg:cargo/tokio","source":"GHSA-rr8g-9fpq-6wmg"},{"ecosystem":"crates.io","fixed":["1.43.1"],"introduced":["1.39.0"],"last_affected":[],"package":"tokio","purl":null,"source":"GHSA-rr8g-9fpq-6wmg"},{"ecosystem":"crates.io","fixed":["1.43.1"],"introduced":["1.39.0"],"last_affected":[],"package":"tokio","purl":"pkg:cargo/tokio","source":"GHSA-rr8g-9fpq-6wmg"},{"ecosystem":"crates.io","fixed":["1.44.2"],"introduced":["1.44.0"],"last_affected":[],"package":"tokio","purl":null,"source":"GHSA-rr8g-9fpq-6wmg"},{"ecosystem":"crates.io","fixed":["1.44.2"],"introduced":["1.44.0"],"last_affected":[],"package":"tokio","purl":"pkg:cargo/tokio","source":"GHSA-rr8g-9fpq-6wmg"}],"products":null,"published":"2025-04-07","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Unsoundness in Rust broadcast channels allows memory corruption when cloning non-Sync values, potentially leading to code execution.","url":"https://insights.sbomify.com/GHSA-rr8g-9fpq-6wmg/"}