GHSA-jwh2-vrr9-vcp2
mz-avro's incorrect use of `set_len` allows for un-initialized memory
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.
What each source reports
GitHub AdvisoriesNo score
mz-avro's incorrect use of `set_len` allows for un-initialized memory
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.
- Record
GHSA-jwh2-vrr9-vcp2- Updated
- 2026-11-02
OSVNo score
mz-avro's incorrect use of `set_len` allows for un-initialized memory
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.
- Record
GHSA-jwh2-vrr9-vcp2- Updated
- 2026-11-02
OSVRUSTSEC-2021-0138No score
Incorrect use of `set_len` allows for un-initialized memory
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.
- Record
RUSTSEC-2021-0138- Updated
- 2026-11-02
Affected packages
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-jwh2-vrr9-vcp2 is a vulnerability with no CVSS score yet in mz-avro, published October 14, 2021. No source lists public exploit code. Fixed in mz-avro 0.7.0.