Summary
Yechan Bae discovered that sized-chunks did not properly validate array
size when constructing Chunk. An attacker could possibly use these
issues to cause out-of-bounds access, leading to memory corruption or
undefined behavior. (CVE-2020-25791, CVE-2020-25792, CVE-2020-25793)
Yechan Bae discovered that sized-chunks had a memory safety issue in the
clone implementation when a panic occurs. An attacker could possibly use
this issue to cause improper memory handling, leading to memory
corruption or a denial of service. (CVE-2020-25794)
Yechan Bae discovered that sized-chunks could create unaligned
references in the InlineArray implementation for types with strict
alignment requirements. An attacker could possibly use this issue to
cause undefined behavior, leading to memory corruption or a denial of
service. (CVE-2020-25796)
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| Ubuntu · Pro 20.04 LTS Pro:20.04:LTS | rust-sized-chunks | 0.3.1-1ubuntu0.1~esm1 |
Vulnerabilities 5
-
High 7.5
Array size is not checked in sized-chunks
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with unit().
-
High 7.5
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size i…
-
Unscored —
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size i…
-
Unscored —
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, clone can have a…
-
Unscored —
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the InlineArray implementation, an unalign…