CVE-2020-25794: Memory Release Issue in sized-chunks Crate
Summary
CVE-2020-25791: Missing release of memory in sized-chunks. Affects sized-chunks versions < 0.6.3. Fixed in 0.6.3. How to fix ↓
Also tracked for
- rust-sized-chunks · Debian:11
- rust-sized-chunks · Debian:11
- rust-sized-chunks · Debian:11
- rust-sized-chunks · Debian:11
- rust-sized-chunks · Debian:11
- rust-sized-chunks · Debian:11
The same CVE-2020-25791 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The sized-chunks crate is a Rust library that provides functionality for working with sized chunks of memory. It allows users to allocate and manage memory in fixed-size chunks. The crate is commonly used in Rust applications that require efficient memory management. However, a vulnerability has been discovered in versions up to 0.6.2 of the sized-chunks crate, which can lead to a memory-safety issue when cloning a Chunk object during a panic.
Vulnerability Detail
The vulnerability in the sized-chunks crate arises from a missing release of memory in the Chunk implementation. When a panic occurs during the cloning of a Chunk object, memory that was allocated for the clone is not properly released. This can result in memory leaks and potential memory corruption. An attacker could potentially exploit this vulnerability to cause a denial-of-service condition or execute arbitrary code with elevated privileges.
How To Fix
Latest published version: 0.7.0 as of 22 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
0.6.3
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to update the sized-chunks crate to the fixed version to mitigate the risk.
Conclusion
In conclusion, the sized-chunks crate up to version 0.6.2 is vulnerable to a memory release issue that can lead to memory leaks and potential memory corruption. It is crucial for developers to update the crate to version 0.6.3 or later to mitigate the risk. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for sized-chunks →
FAQ
This vulnerability can lead to memory leaks and potential memory corruption. It could be exploited by an attacker to cause a denial-of-service condition or execute arbitrary code with elevated privileges.
Versions up to and including 0.6.2 of the sized-chunks crate are affected by this vulnerability.
No, there is no known workaround for this vulnerability. Updating to the fixed version is necessary.
To update the sized-chunks crate, modify the dependency version in your Cargo.toml file to 0.6.3 or later and run the cargo update command.
For more information about this vulnerability, you can refer to the GitHub Advisory Database entry: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/08/GHSA-rfgg-vccr-m46m/GHSA-rfgg-vccr-m46m.json
Related vulnerabilities
Recent vulnerabilities recorded for sized-chunks.
