{"answers":{"affected":"3 open source packages ship an affected version, including mz-avro.","exploited":"There is no known exploitation of GHSA-jwh2-vrr9-vcp2 in the wild and no public exploit code.","fix":"Upgrade mz-avro to 0.7.0 or later.","what":"GHSA-jwh2-vrr9-vcp2 is a memory corruption vulnerability in mz-avro, published on 14 Oct 2021."},"fix_prompt":"Check this codebase for GHSA-jwh2-vrr9-vcp2 and fix it if it is affected.\n\nWhat it is: GHSA-jwh2-vrr9-vcp2 is a memory corruption vulnerability in mz-avro, published on 14 Oct 2021. \nExploitation: There is no known exploitation of GHSA-jwh2-vrr9-vcp2 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mz-avro (crates.io): affected all versions; fixed in 0.7.0\n- mz-avro (crates.io): affected all versions; fixed in 0.7.0\n- mz-avro (crates.io): affected from 0.0.0-0; fixed in 0.7.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-jwh2-vrr9-vcp2/ (Markdown: https://insights.sbomify.com/GHSA-jwh2-vrr9-vcp2/index.md)","id":"GHSA-jwh2-vrr9-vcp2","markdown":"https://insights.sbomify.com/GHSA-jwh2-vrr9-vcp2/index.md","name":"GHSA-jwh2-vrr9-vcp2","record":{"aliases":["RUSTSEC-2021-0138"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","other"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust Avro library","requires_auth":"none","summary":"Attackers can exploit unidiomatic Read implementations to expose uninitialized memory or cause undefined behavior in applications using the mz-avro crate.","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 this crate passes an uninitialized buffer to a user-provided `Read` \nimplementation.\n\nArbitrary `Read` implementations can read from the uninitialized buffer (memory exposure)\nand also can return incorrect number of bytes written to the buffer.\nReading from uninitialized memory produces undefined values that can quickly invoke\nundefined behavior.\n\nNote: there is only UB in the case where a user provides a struct whose `Read`\nimplementation inspects the buffer passed to `read_exact` before writing to it.\nThis is an unidiomatic (albeit possible) `Read` implementation.\n\nSee https://github.com/MaterializeInc/materialize/issues/8669 for details.","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":"mz-avro's incorrect use of `set_len` allows for un-initialized memory","id":"GHSA-jwh2-vrr9-vcp2","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.7.0"],"introduced":["0"],"last_affected":[],"package":"mz-avro","purl":null,"source":"GHSA-jwh2-vrr9-vcp2"},{"ecosystem":"crates.io","fixed":["0.7.0"],"introduced":["0"],"last_affected":[],"package":"mz-avro","purl":"pkg:cargo/mz-avro","source":"GHSA-jwh2-vrr9-vcp2"},{"ecosystem":"crates.io","fixed":["0.7.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"mz-avro","purl":"pkg:cargo/mz-avro","source":"RUSTSEC-2021-0138"}],"products":null,"published":"2021-10-14","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 exploit unidiomatic Read implementations to expose uninitialized memory or cause undefined behavior in applications using the mz-avro crate.","url":"https://insights.sbomify.com/GHSA-jwh2-vrr9-vcp2/"}