{"answers":{"affected":"3 open source packages ship an affected version, including memoffset.","exploited":"There is no known exploitation of GHSA-wfg4-322g-9vqv in the wild and no public exploit code.","fix":"Upgrade memoffset to 0.6.2 or later.","what":"GHSA-wfg4-322g-9vqv is a memory corruption vulnerability in memoffset, published on 21 Jun 2023."},"fix_prompt":"Check this codebase for GHSA-wfg4-322g-9vqv and fix it if it is affected.\n\nWhat it is: GHSA-wfg4-322g-9vqv is a memory corruption vulnerability in memoffset, published on 21 Jun 2023. \nExploitation: There is no known exploitation of GHSA-wfg4-322g-9vqv in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- memoffset (crates.io): affected all versions; fixed in 0.6.2\n- memoffset (crates.io): affected all versions; fixed in 0.6.2\n- memoffset (crates.io): affected from 0.0.0-0; fixed in 0.6.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-wfg4-322g-9vqv/ (Markdown: https://insights.sbomify.com/GHSA-wfg4-322g-9vqv/index.md)","id":"GHSA-wfg4-322g-9vqv","markdown":"https://insights.sbomify.com/GHSA-wfg4-322g-9vqv/index.md","name":"GHSA-wfg4-322g-9vqv","record":{"aliases":["RUSTSEC-2023-0045"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust memory offset library","requires_auth":"none","summary":"The memoffset library allows reading uninitialized memory, potentially causing undefined behavior, crashes, or code execution in Rust applications.","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":"memoffset allows attempt of reading data from address `0` with arbitrary type. This behavior is an undefined behavior because address `0` to `std::mem::size_of\u003cT\u003e` may not have valid bit-pattern with `T`. Old implementation dereferences uninitialized memory obtained from `std::mem::align_of`. Older implementation prior to it allows using uninitialized data obtained from `std::mem::uninitialized` with arbitrary type then compute offset by taking the address of field-projection. This may also result in an undefined behavior for \"father\" that includes (directly or transitively) type that [does not allow to be uninitialized](https://doc.rust-lang.org/nightly/reference/behavior-considered-undefined.html).\n\nThis flaw was corrected by using `std::ptr::addr_of` in \u003chttps://github.com/Gilnaa/memoffset/pull/50\u003e.","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":"memoffset allows reading uninitialized memory","id":"GHSA-wfg4-322g-9vqv","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":["0.6.2"],"introduced":["0"],"last_affected":[],"package":"memoffset","purl":null,"source":"GHSA-wfg4-322g-9vqv"},{"ecosystem":"crates.io","fixed":["0.6.2"],"introduced":["0"],"last_affected":[],"package":"memoffset","purl":"pkg:cargo/memoffset","source":"GHSA-wfg4-322g-9vqv"},{"ecosystem":"crates.io","fixed":["0.6.2"],"introduced":["0.0.0-0"],"last_affected":[],"package":"memoffset","purl":"pkg:cargo/memoffset","source":"RUSTSEC-2023-0045"}],"products":null,"published":"2023-06-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":"The memoffset library allows reading uninitialized memory, potentially causing undefined behavior, crashes, or code execution in Rust applications.","url":"https://insights.sbomify.com/GHSA-wfg4-322g-9vqv/"}