{"answers":{"affected":"3 open source packages ship an affected version, including array-queue.","exploited":"There is no known exploitation of GHSA-xqjr-wfx3-gmxv in the wild and no public exploit code.","fix":"Upgrade array-queue to 0.4.0 or later.","what":"GHSA-xqjr-wfx3-gmxv is a memory corruption vulnerability in array-queue, published on 14 Aug 2025."},"fix_prompt":"Check this codebase for GHSA-xqjr-wfx3-gmxv and fix it if it is affected.\n\nWhat it is: GHSA-xqjr-wfx3-gmxv is a memory corruption vulnerability in array-queue, published on 14 Aug 2025. \nExploitation: There is no known exploitation of GHSA-xqjr-wfx3-gmxv in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- array-queue (crates.io): affected from 0.3.0; fixed in 0.4.0\n- array-queue (crates.io): affected from 0.3.0; fixed in 0.4.0\n- array-queue (crates.io): affected from 0.3.0; fixed in 0.4.0\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-xqjr-wfx3-gmxv/ (Markdown: https://insights.sbomify.com/GHSA-xqjr-wfx3-gmxv/index.md)","id":"GHSA-xqjr-wfx3-gmxv","markdown":"https://insights.sbomify.com/GHSA-xqjr-wfx3-gmxv/index.md","name":"GHSA-xqjr-wfx3-gmxv","record":{"aliases":["RUSTSEC-2025-0054"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust ArrayQueue library","requires_auth":"none","summary":"A panic during cloning in ArrayQueue's push_front causes the destructor to free uninitialized memory, potentially leading to crashes or 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 safe API `array_queue::ArrayQueue::push_front` can lead to deallocating uninitialized memory if a panic occurs while invoking the `clone` method on the passed argument.\n\nSpecifically, `push_front` receives an argument that is intended to be cloned and pushed, whose type implements the `Clone` trait. Furthermore, the method updates the queue's `start` index before initializing the slot for the newly pushed element. User-defined implementations of `Clone` may include a `clone` method that can panic. If such a panic occurs during initialization, the structure is left with an advanced `start` index pointing to an uninitialized slot. When `ArrayQueue` is later dropped, its destructor treats that slot as initialized and attempts to drop it, resulting in an attempt to free uninitialized memory.\n\nThe bug was fixed in commit `728fe1b`.","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":"ArrayQueue's push_front is not panic-safe","id":"GHSA-xqjr-wfx3-gmxv","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.4.0"],"introduced":["0.3.0"],"last_affected":[],"package":"array-queue","purl":null,"source":"GHSA-xqjr-wfx3-gmxv"},{"ecosystem":"crates.io","fixed":["0.4.0"],"introduced":["0.3.0"],"last_affected":[],"package":"array-queue","purl":"pkg:cargo/array-queue","source":"GHSA-xqjr-wfx3-gmxv"},{"ecosystem":"crates.io","fixed":["0.4.0"],"introduced":["0.3.0"],"last_affected":[],"package":"array-queue","purl":"pkg:cargo/array-queue","source":"RUSTSEC-2025-0054"}],"products":null,"published":"2025-08-14","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":"A panic during cloning in ArrayQueue's push_front causes the destructor to free uninitialized memory, potentially leading to crashes or code execution.","url":"https://insights.sbomify.com/GHSA-xqjr-wfx3-gmxv/"}