{"answers":{"affected":"3 open source packages ship an affected version, including static-alloc.","exploited":"There is no known exploitation of GHSA-xrrq-rrgq-h89w in the wild and no public exploit code.","fix":"Upgrade static-alloc to 0.2.6 or later.","what":"GHSA-xrrq-rrgq-h89w is a memory corruption vulnerability in static-alloc, published on 11 Jul 2025."},"fix_prompt":"Check this codebase for GHSA-xrrq-rrgq-h89w and fix it if it is affected.\n\nWhat it is: GHSA-xrrq-rrgq-h89w is a memory corruption vulnerability in static-alloc, published on 11 Jul 2025. \nExploitation: There is no known exploitation of GHSA-xrrq-rrgq-h89w in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- static-alloc (crates.io): affected from 0.2.2; fixed in 0.2.6\n- static-alloc (crates.io): affected from 0.2.2; fixed in 0.2.6\n- static-alloc (crates.io): affected from 0.2.2-0; fixed in 0.2.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/GHSA-xrrq-rrgq-h89w/ (Markdown: https://insights.sbomify.com/GHSA-xrrq-rrgq-h89w/index.md)","id":"GHSA-xrrq-rrgq-h89w","markdown":"https://insights.sbomify.com/GHSA-xrrq-rrgq-h89w/index.md","name":"GHSA-xrrq-rrgq-h89w","record":{"aliases":["RUSTSEC-2025-0042"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust memory allocator","requires_auth":"none","summary":"An uninitialized memory read in MemBump allocation can cause assertion failures and denial of service in Rust applications using this library.","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 affected function, `MemBump::new()`, would allocate memory without\ninitializing it. Subsequently calling the created value's various `alloc`\nmethods would then read and write the start of that memory as a `Cell` which is\nundefined behavior. Instead, it should zero initialize the start of the\nallocated memory.\n\nFor instance, some values could violate the internal invariants of the type and\ncause an assertion failure. Nevertheless, no deterministic read is known to\ncause further uninitialized memory to be exposed.\n\nAffected downstream users that can not upgrade are advised to call\n`MemBump::reset` immediately after allocation to manually perform the missing\nwrite of the counter best-as-possible.\n\nThe flaw was corrected in commit d8d6a7d096d3aaafd963b356a8f1bbd8d26fd967 by\nzeroing the Cell at the start of the allocated memory.","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":"Uninitialized read after allocating MemBump","id":"GHSA-xrrq-rrgq-h89w","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.2.6"],"introduced":["0.2.2"],"last_affected":[],"package":"static-alloc","purl":null,"source":"GHSA-xrrq-rrgq-h89w"},{"ecosystem":"crates.io","fixed":["0.2.6"],"introduced":["0.2.2"],"last_affected":[],"package":"static-alloc","purl":"pkg:cargo/static-alloc","source":"GHSA-xrrq-rrgq-h89w"},{"ecosystem":"crates.io","fixed":["0.2.6"],"introduced":["0.2.2-0"],"last_affected":[],"package":"static-alloc","purl":"pkg:cargo/static-alloc","source":"RUSTSEC-2025-0042"}],"products":null,"published":"2025-07-11","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":"An uninitialized memory read in MemBump allocation can cause assertion failures and denial of service in Rust applications using this library.","url":"https://insights.sbomify.com/GHSA-xrrq-rrgq-h89w/"}