{"answers":{"affected":"3 open source packages ship an affected version, including direct_ring_buffer.","exploited":"There is no known exploitation of GHSA-fp5x-7m4q-449f in the wild and no public exploit code.","fix":"Upgrade direct_ring_buffer to 0.2.2 or later.","what":"GHSA-fp5x-7m4q-449f is a memory corruption vulnerability in direct_ring_buffer, published on 21 Oct 2025."},"fix_prompt":"Check this codebase for GHSA-fp5x-7m4q-449f and fix it if it is affected.\n\nWhat it is: GHSA-fp5x-7m4q-449f is a memory corruption vulnerability in direct_ring_buffer, published on 21 Oct 2025. \nExploitation: There is no known exploitation of GHSA-fp5x-7m4q-449f in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- direct_ring_buffer (crates.io): affected all versions; fixed in 0.2.2\n- direct_ring_buffer (crates.io): affected all versions; fixed in 0.2.2\n- direct_ring_buffer (crates.io): affected from 0.0.0-0; fixed in 0.2.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-fp5x-7m4q-449f/ (Markdown: https://insights.sbomify.com/GHSA-fp5x-7m4q-449f/index.md)","id":"GHSA-fp5x-7m4q-449f","markdown":"https://insights.sbomify.com/GHSA-fp5x-7m4q-449f/index.md","name":"GHSA-fp5x-7m4q-449f","record":{"aliases":["RUSTSEC-2025-0105"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust ring buffer library","requires_auth":"none","summary":"Uninitialized memory exposure in create_ring_buffer allows undefined behavior, potentially leading to code execution or information disclosure.","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 function `create_ring_buffer` allocates a buffer using `Vec::with_capacity` followed by `set_len`, creating a `Box\u003c[T]\u003e` containing uninitialized memory.\n\nThis leads to undefined behavior when functions like `write_slices` create typed slices (e.g., `\u0026mut [bool]`) over the uninitialized memory, violating Rust's validity invariants. The issue has been confirmed using Miri.\n\nFixed in version 0.2.2 by using `resize_with` to properly initialize the buffer with `T::default()`, adding a `T: Default` bound to ensure sound initialization.","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":"Direct Ring Buffer has uninitialized memory exposure in create_ring_buffer","id":"GHSA-fp5x-7m4q-449f","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.2"],"introduced":["0"],"last_affected":[],"package":"direct_ring_buffer","purl":null,"source":"GHSA-fp5x-7m4q-449f"},{"ecosystem":"crates.io","fixed":["0.2.2"],"introduced":["0"],"last_affected":[],"package":"direct_ring_buffer","purl":"pkg:cargo/direct_ring_buffer","source":"GHSA-fp5x-7m4q-449f"},{"ecosystem":"crates.io","fixed":["0.2.2"],"introduced":["0.0.0-0"],"last_affected":[],"package":"direct_ring_buffer","purl":"pkg:cargo/direct_ring_buffer","source":"RUSTSEC-2025-0105"}],"products":null,"published":"2025-10-21","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":"Uninitialized memory exposure in create_ring_buffer allows undefined behavior, potentially leading to code execution or information disclosure.","url":"https://insights.sbomify.com/GHSA-fp5x-7m4q-449f/"}