claxon
Affected
- introduced
0.0.0-0, fixed0.3.2, introduced0.4.0-0, fixed0.4.1(semver)
Fixed versions
0.3.2, 0.4.1
Fix
- Fixed version
0.3.2cargo update -p claxon --precise 0.3.2 - Fixed version
0.4.1cargo update -p claxon --precise 0.4.1
Advisory
Also known as: CVE-2018-20992, GHSA-8c6g-4xc5-w96c
Malicious input could cause uninitialized memory to be exposed
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.
Medium Basis: CVSS v3 score 6.5, vector CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
0.0.0-0, fixed 0.3.2, introduced 0.4.0-0, fixed 0.4.1 (semver)0.3.2, 0.4.1
0.3.2cargo update -p claxon --precise 0.3.20.4.1cargo update -p claxon --precise 0.4.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0