RUSTSEC-2018-0004

Malicious input could cause uninitialized memory to be exposed

Reported

August 25, 2018

Issued

October 1, 2020 (last modified: June 13, 2023)

Package

claxon (crates.io)

Type

Vulnerability

Keywords

#uninitialized-memory

Aliases

References

https://github.com/ruuda/claxon/commit/8f28ec275e412dd3af4f3cda460605512faf332c

CVSS Score

6.5 MEDIUM

CVSS Details

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

CVSS Vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Patched

^0.3.2
>=0.4.1

Description

Affected versions of Claxon made an invalid assumption about the decode buffer size being a multiple of a value read from the bitstream. This could cause parts of the decode buffer to not be overwritten. If the decode buffer was newly allocated and uninitialized, this uninitialized memory could be exposed.

This allows an attacker to observe parts of the uninitialized memory in the decoded audio stream.

The flaw was corrected by checking that the value read from the bitstream divides the decode buffer size, and returning a format error if it does not. If an error is returned, the decode buffer is not exposed. Regression tests and an additional fuzzer have been added to prevent similar flaws in the future.

Advisory available under CC0-1.0 license.