GHSA-jwh2-vrr9-vcp2: Mz avro Mz-avro's Incorrect Use Of `set_len` Vulnerability

MODERATE
Share
Published
Advisory Summary

GHSA-jwh2-vrr9-vcp2 is a MODERATE mz-avro's incorrect use of `set_len` vulnerability (General Security Weakness) affecting Mz avro libraries in the crates.io ecosystem. The issue involves mz-avro's incorrect use of `set_len` allows for un-initialized memory. Remediation is available by upgrading affected packages to version 0.7.0.

GHSA-jwh2-vrr9-vcp2 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-jwh2-vrr9-vcp2
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Mz avro
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-jwh2-vrr9-vcp2

To remediate this vulnerability, upgrade all affected Mz avro dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

mz-avro fixed: 0.7.0 
Upgrade mz-avro to 0.7.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for mz-avro

How to Check if You Are Affected

To determine whether your application is affected by GHSA-jwh2-vrr9-vcp2, inspect your project dependencies for Mz avro:

inspect dependencies for mz-avro

Analyze the terminal output to locate any version of Mz avro in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.7.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Mz avro, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

GHSA-jwh2-vrr9-vcp2 Affected Mz avro Versions

1 component(s)
Fixed Versions:
0.7.0
Product / Package Ecosystem Affected Versions Fixed Version
mz-avro
 crates.io
< 0.7.0
0.7.0

References

Mz avro Source Repository REPOSITORY
https://github.com/MaterializeInc/materialize/issues/8669
Mz avro Source Repository REPOSITORY
https://github.com/MaterializeInc/materialize
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2021-0138.html

Frequently Asked Questions

What is GHSA-jwh2-vrr9-vcp2?
GHSA-jwh2-vrr9-vcp2 is a security vulnerability in Mz avro involving mz-avro's incorrect use of `set_len` allows for un-initialized memory under General Security Weakness.
Which Mz avro versions are affected?
Affected versions include releases prior to 0.7.0 across affected packages: mz-avro.
What version fixes GHSA-jwh2-vrr9-vcp2?
Upgrading to 0.7.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is mz-avro affected?
Yes, mz-avro is affected in releases prior to 0.7.0. Upgrade your dependency to 0.7.0 or later.
What CWE is associated with GHSA-jwh2-vrr9-vcp2?
GHSA-jwh2-vrr9-vcp2 is classified under General Security Weakness.
How can I check crates.io dependencies for GHSA-jwh2-vrr9-vcp2?
Run the dependency tree command: 'inspect dependencies for mz-avro'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jwh2-vrr9-vcp2",
  "modified" : "2022-08-30T19:53:54Z",
  "published" : "2022-08-30T19:53:54Z",
  "aliases" : [ ],
  "summary" : "mz-avro's incorrect use of `set_len` allows for un-initialized memory",
  "details" : "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.\n",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "mz-avro"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.7.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/MaterializeInc/materialize/issues/8669"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/MaterializeInc/materialize"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2021-0138.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-08-30T19:53:54Z",
    "nvd_published_at" : null
  }
}