{"answers":{"affected":"3 open source packages ship an affected version, including crossbeam-queue.","exploited":"There is no known exploitation of GHSA-6888-wf7j-34jq in the wild and no public exploit code.","fix":"Upgrade crossbeam-queue to 0.2.3 or later.","what":"GHSA-6888-wf7j-34jq is a memory corruption vulnerability in crossbeam-queue, published on 10 May 2022."},"fix_prompt":"Check this codebase for GHSA-6888-wf7j-34jq and fix it if it is affected.\n\nWhat it is: GHSA-6888-wf7j-34jq is a memory corruption vulnerability in crossbeam-queue, published on 10 May 2022. \nExploitation: There is no known exploitation of GHSA-6888-wf7j-34jq in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- crossbeam-queue (crates.io): affected all versions; fixed in 0.2.3\n- crossbeam-queue (crates.io): affected all versions; fixed in 0.2.3\n- crossbeam-queue (crates.io): affected from 0.0.0-0; fixed in 0.2.3\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-6888-wf7j-34jq/ (Markdown: https://insights.sbomify.com/GHSA-6888-wf7j-34jq/index.md)","id":"GHSA-6888-wf7j-34jq","markdown":"https://insights.sbomify.com/GHSA-6888-wf7j-34jq/index.md","name":"GHSA-6888-wf7j-34jq","record":{"aliases":["RUSTSEC-2022-0021"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust concurrent queue","requires_auth":"none","summary":"Unsound memory initialization in SegQueue can cause null pointer dereferences or memory corruption, potentially leading to crashes or arbitrary 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":"Affected versions of this crate called `mem::zeroed()` to create values of a user-supplied type `T`.\nThis is unsound e.g. if `T` is a reference type (which must be non-null).\n \nThe flaw was corrected by avoiding the use of `mem::zeroed()`, using `MaybeUninit` instead.","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":"`SegQueue` creates zero value of any type","id":"GHSA-6888-wf7j-34jq","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.2.3"],"introduced":["0"],"last_affected":[],"package":"crossbeam-queue","purl":null,"source":"GHSA-6888-wf7j-34jq"},{"ecosystem":"crates.io","fixed":["0.2.3"],"introduced":["0"],"last_affected":[],"package":"crossbeam-queue","purl":"pkg:cargo/crossbeam-queue","source":"GHSA-6888-wf7j-34jq"},{"ecosystem":"crates.io","fixed":["0.2.3"],"introduced":["0.0.0-0"],"last_affected":[],"package":"crossbeam-queue","purl":"pkg:cargo/crossbeam-queue","source":"RUSTSEC-2022-0021"}],"products":null,"published":"2022-05-10","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":"Unsound memory initialization in SegQueue can cause null pointer dereferences or memory corruption, potentially leading to crashes or arbitrary code execution.","url":"https://insights.sbomify.com/GHSA-6888-wf7j-34jq/"}