{"answers":{"affected":"5 open source packages ship an affected version, including zerovec-derive.","exploited":"There is no known exploitation of GHSA-74r5-g7vc-j2v2 in the wild and no public exploit code.","fix":"Upgrade zerovec-derive to a fixed version for your release line: 0.9.7 or 0.10.3.","what":"GHSA-74r5-g7vc-j2v2 is a memory corruption vulnerability in zerovec-derive, published on 1 Jul 2024."},"fix_prompt":"Check this codebase for GHSA-74r5-g7vc-j2v2 and fix it if it is affected.\n\nWhat it is: GHSA-74r5-g7vc-j2v2 is a memory corruption vulnerability in zerovec-derive, published on 1 Jul 2024. \nExploitation: There is no known exploitation of GHSA-74r5-g7vc-j2v2 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- zerovec-derive (crates.io): affected all versions; fixed in 0.9.7\n- zerovec-derive (crates.io): affected all versions; fixed in 0.9.7\n- zerovec-derive (crates.io): affected from 0.0.0-0; fixed in 0.9.7, 0.10.3\n- zerovec-derive (crates.io): affected from 0.10.0; fixed in 0.10.3\n- zerovec-derive (crates.io): affected from 0.10.0; fixed in 0.10.3\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-74r5-g7vc-j2v2/ (Markdown: https://insights.sbomify.com/GHSA-74r5-g7vc-j2v2/index.md)","id":"GHSA-74r5-g7vc-j2v2","markdown":"https://insights.sbomify.com/GHSA-74r5-g7vc-j2v2/index.md","name":"GHSA-74r5-g7vc-j2v2","record":{"aliases":["RUSTSEC-2024-0346"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust derive macro","requires_auth":"none","summary":"Attackers can trigger illegal memory accesses and potential code execution in applications using the zerovec-derive crate due to incorrect struct layout assumptions.","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 versions make unsafe memory accesses under the assumption that `#[repr(packed)]` has a guaranteed field order. \n\nThe Rust specification does not guarantee this, and https://github.com/rust-lang/rust/pull/125360 (1.80.0-beta) starts \nreordering fields of `#[repr(packed)]` structs, leading to illegal memory accesses.\n\nThe patched versions `0.9.7` and `0.10.3` use `#[repr(C, packed)]`, which guarantees field order.","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":"zerovec-derive incorrectly uses `#[repr(packed)]`","id":"GHSA-74r5-g7vc-j2v2","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":5,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.9.7"],"introduced":["0"],"last_affected":[],"package":"zerovec-derive","purl":null,"source":"GHSA-74r5-g7vc-j2v2"},{"ecosystem":"crates.io","fixed":["0.9.7"],"introduced":["0"],"last_affected":[],"package":"zerovec-derive","purl":"pkg:cargo/zerovec-derive","source":"GHSA-74r5-g7vc-j2v2"},{"ecosystem":"crates.io","fixed":["0.9.7","0.10.3"],"introduced":["0.0.0-0","0.10.0"],"last_affected":[],"package":"zerovec-derive","purl":"pkg:cargo/zerovec-derive","source":"RUSTSEC-2024-0346"},{"ecosystem":"crates.io","fixed":["0.10.3"],"introduced":["0.10.0"],"last_affected":[],"package":"zerovec-derive","purl":null,"source":"GHSA-74r5-g7vc-j2v2"},{"ecosystem":"crates.io","fixed":["0.10.3"],"introduced":["0.10.0"],"last_affected":[],"package":"zerovec-derive","purl":"pkg:cargo/zerovec-derive","source":"GHSA-74r5-g7vc-j2v2"}],"products":null,"published":"2024-07-01","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 trigger illegal memory accesses and potential code execution in applications using the zerovec-derive crate due to incorrect struct layout assumptions.","url":"https://insights.sbomify.com/GHSA-74r5-g7vc-j2v2/"}