RUSTSEC-2021-0138

See a problem?
Please try reporting it to the source first.
Source
https://rustsec.org/advisories/RUSTSEC-2021-0138
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2021-0138.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2021-0138
Aliases
Published
2021-10-14T12:00:00Z
Modified
2023-11-08T04:20:47.718056Z
Summary
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 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.

Database specific 
{
    "license": "CC0-1.0"
}
References

Affected packages

crates.io / mz-avro

Package

Name
mz-avro
View open source insights on deps.dev
Purl
pkg:cargo/mz-avro

Affected ranges

Type
SEMVER
Events
Introduced
0.0.0-0
Fixed
0.7.0

Ecosystem specific 

{
    "affected_functions": null,
    "affects": {
        "os": [],
        "functions": [],
        "arch": []
    }
}

Database specific 

{
    "cvss": null,
    "informational": "unsound",
    "categories": [
        "memory-exposure"
    ]
}