{"answers":{"affected":"3 open source packages ship an affected version, including inventory.","exploited":"There is no known exploitation of GHSA-36xm-35qq-795w in the wild and no public exploit code.","fix":"Upgrade inventory to 0.2.0 or later.","what":"GHSA-36xm-35qq-795w is a vulnerability in inventory, published on 10 Sep 2023."},"fix_prompt":"Check this codebase for GHSA-36xm-35qq-795w and fix it if it is affected.\n\nWhat it is: GHSA-36xm-35qq-795w is a vulnerability in inventory, published on 10 Sep 2023. \nExploitation: There is no known exploitation of GHSA-36xm-35qq-795w in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- inventory (crates.io): affected all versions; fixed in 0.2.0\n- inventory (crates.io): affected all versions; fixed in 0.2.0\n- inventory (crates.io): affected from 0.0.0-0; fixed in 0.2.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-36xm-35qq-795w/ (Markdown: https://insights.sbomify.com/GHSA-36xm-35qq-795w/index.md)","id":"GHSA-36xm-35qq-795w","markdown":"https://insights.sbomify.com/GHSA-36xm-35qq-795w/index.md","name":"GHSA-36xm-35qq-795w","record":{"aliases":["RUSTSEC-2023-0058"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust inventory crate","requires_auth":"none","summary":"The inventory crate allows thread-unsafe data to be accessed concurrently, potentially causing race conditions, crashes, or memory corruption in Rust applications.","user_interaction":"not_required","vuln_class":"race_condition"},"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 do not enforce a `Sync` bound on the type of caller-provided\nvalue held in the plugin registry. References to these values are made\naccessible to arbitrary threads other than the one that constructed them.\n\nA caller could use this flaw to submit thread-unsafe data into inventory, then\naccess it as a reference simultaneously from multiple threads.\n\nThe flaw was corrected by enforcing that data submitted by the caller into\ninventory is `Sync`.","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":"Exposes reference to non-Sync data to an arbitrary thread","id":"GHSA-36xm-35qq-795w","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"race_condition","year":"2023"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.2.0"],"introduced":["0"],"last_affected":[],"package":"inventory","purl":null,"source":"GHSA-36xm-35qq-795w"},{"ecosystem":"crates.io","fixed":["0.2.0"],"introduced":["0"],"last_affected":[],"package":"inventory","purl":"pkg:cargo/inventory","source":"GHSA-36xm-35qq-795w"},{"ecosystem":"crates.io","fixed":["0.2.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"inventory","purl":"pkg:cargo/inventory","source":"RUSTSEC-2023-0058"}],"products":null,"published":"2023-09-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":"The inventory crate allows thread-unsafe data to be accessed concurrently, potentially causing race conditions, crashes, or memory corruption in Rust applications.","url":"https://insights.sbomify.com/GHSA-36xm-35qq-795w/"}