{"answers":{"affected":"3 open source packages ship an affected version, including borsh.","exploited":"There is no known exploitation of GHSA-fjx5-qpf4-xjf2 in the wild and no public exploit code.","fix":"Upgrade borsh to a fixed version for your release line: 1.0.0-alpha.1 or 0.10.4.","what":"GHSA-fjx5-qpf4-xjf2 is a memory corruption vulnerability in borsh, published on 12 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-fjx5-qpf4-xjf2 and fix it if it is affected.\n\nWhat it is: GHSA-fjx5-qpf4-xjf2 is a memory corruption vulnerability in borsh, published on 12 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-fjx5-qpf4-xjf2 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- borsh (crates.io): affected all versions; fixed in 1.0.0-alpha.1\n- borsh (crates.io): affected all versions; fixed in 1.0.0-alpha.1\n- borsh (crates.io): affected from 0.0.0-0; fixed in 0.10.4, 1.0.0-alpha.1\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-fjx5-qpf4-xjf2/ (Markdown: https://insights.sbomify.com/GHSA-fjx5-qpf4-xjf2/index.md)","id":"GHSA-fjx5-qpf4-xjf2","markdown":"https://insights.sbomify.com/GHSA-fjx5-qpf4-xjf2/index.md","name":"GHSA-fjx5-qpf4-xjf2","record":{"aliases":["RUSTSEC-2023-0033"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust serialization library","requires_auth":"none","summary":"Attackers can cause segmentation faults or potential code execution by deserializing zero-sized types that lack Copy/Clone traits in the borsh 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":"Affected versions of borsh cause undefined behavior when zero-sized-types (ZST) are parsed and the Copy/Clone traits are not implemented/derived. For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy (this can be achieved through a singleton), then accessing/writing to deserialized data will cause a segmentation fault.\n\nThere is currently no way for borsh to read data without also providing a Rust type. Therefore, if you are not using ZST for serialization, then you are not affected by this issue.","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":"Parsing borsh messages with ZST which are not-copy/clone is unsound","id":"GHSA-fjx5-qpf4-xjf2","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["1.0.0-alpha.1"],"introduced":["0"],"last_affected":[],"package":"borsh","purl":null,"source":"GHSA-fjx5-qpf4-xjf2"},{"ecosystem":"crates.io","fixed":["1.0.0-alpha.1"],"introduced":["0"],"last_affected":[],"package":"borsh","purl":"pkg:cargo/borsh","source":"GHSA-fjx5-qpf4-xjf2"},{"ecosystem":"crates.io","fixed":["0.10.4","1.0.0-alpha.1"],"introduced":["0.0.0-0","0.11.0-0"],"last_affected":[],"package":"borsh","purl":"pkg:cargo/borsh","source":"RUSTSEC-2023-0033"}],"products":null,"published":"2023-04-12","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":"Attackers can cause segmentation faults or potential code execution by deserializing zero-sized types that lack Copy/Clone traits in the borsh library.","url":"https://insights.sbomify.com/GHSA-fjx5-qpf4-xjf2/"}