Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

mz-avro

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Unratedcrates.ioPublished

    mz-avro's incorrect use of set_len allows for un-initialized memory

    GHSA-jwh2-vrr9-vcp2

    Affected
    • crates.io mz-avro < 0.7.0
    Fixed in
    0.7.0· Vendor fix available
    Issue
    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 readexact before writing to it. This is an unidiomatic (albeit possible) Read implementation. See https://github.com/MaterializeInc/materialize/issues/8669 for details.

    Recommended action: Upgrade to 0.7.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →