VDB
Sign up
MEDIUM6.5

GHSA-8c6g-4xc5-w96c

Uninitialized memory exposure in claxon

Details

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.

Are you affected?

Enter the version of the package you're using.

Affected packages

crates.io/claxon
Introduced in: 0.4.0Fixed in: 0.4.1

Upgrade claxon to 0.4.1 or newer (ecosystem crates.io).

crates.io/claxon
Introduced in: 0Fixed in: 0.3.2

Upgrade claxon to 0.3.2 or newer (ecosystem crates.io).

References