An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, clone can have a memory-safety issue upon a panic.
Weakness
The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Sized-chunks |
Sized-chunks_project |
* |
0.6.2 (including) |
| Rust-sized-chunks |
Ubuntu |
groovy |
* |
| Rust-sized-chunks |
Ubuntu |
hirsute |
* |
| Rust-sized-chunks |
Ubuntu |
impish |
* |
| Rust-sized-chunks |
Ubuntu |
kinetic |
* |
| Rust-sized-chunks |
Ubuntu |
lunar |
* |
| Rust-sized-chunks |
Ubuntu |
mantic |
* |
| Rust-sized-chunks |
Ubuntu |
trusty |
* |
Potential Mitigations
- Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
- For example, glibc in Linux provides protection against free of invalid pointers.
- When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
- To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.
References