CVE-2018-20992: Uninitialized memory exposure in claxon
(updated )
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.
References
- github.com/advisories/GHSA-8c6g-4xc5-w96c
- github.com/ruuda/claxon
- github.com/ruuda/claxon/commit/8f28ec275e412dd3af4f3cda460605512faf332c
- github.com/ruuda/claxon/releases/tag/v0.3.2
- github.com/ruuda/claxon/releases/tag/v0.4.1
- nvd.nist.gov/vuln/detail/CVE-2018-20992
- rustsec.org/advisories/RUSTSEC-2018-0004.html
Detect and mitigate CVE-2018-20992 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →