Advisory Database
  • Advisories
  • Dependency Scanning
  1. cargo
  2. ›
  3. mz-avro
  4. ›
  5. GHSA-jwh2-vrr9-vcp2

GHSA-jwh2-vrr9-vcp2: mz-avro's incorrect use of `set_len` allows for un-initialized memory

August 30, 2022

Affected versions of this crate passes an uninitialized buffer to a user-provided Read implementation.

Arbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.

Note: there is only UB in the case where a user provides a struct whose Read implementation inspects the buffer passed to read_exact before writing to it. This is an unidiomatic (albeit possible) Read implementation.

See https://github.com/MaterializeInc/materialize/issues/8669 for details.

References

  • github.com/MaterializeInc/materialize
  • github.com/MaterializeInc/materialize/issues/8669
  • github.com/advisories/GHSA-jwh2-vrr9-vcp2
  • rustsec.org/advisories/RUSTSEC-2021-0138.html

Code Behaviors & Features

Detect and mitigate GHSA-jwh2-vrr9-vcp2 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 0.7.0

Fixed versions

  • 0.7.0

Solution

Upgrade to version 0.7.0 or above.

Source file

cargo/mz-avro/GHSA-jwh2-vrr9-vcp2.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 14 May 2025 12:14:52 +0000.