Three removal and replacement paths destroy an initialized value before committing the metadata change that removes it. Destruction runs T::drop(), which is user code and may panic. If it does, the commit is skipped and the container still claims ownership of the already-destroye...
Product
crates.io stack_dst vulnerabilities
3 published CVES affecting crates.io stack_dst, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 3
- Critical
- 2
- High
- 0
- Medium
- 0
- Low
- 0
- Unscored
- 1
- CISA KEV
- 0
Latest crates.io stack_dst CVEs
Newest publication first
-
Unknown
-
CVE-2021-28034 Double free in stack_dst
PublishedCriticalCVSS 9.8 EPSS 1.3%An issue was discovered in the stack_dst crate before 0.6.1 for Rust. Because of the push_inner behavior, a double free can occur upon a val.clone() panic.
-
CriticalCVSS 9.8 EPSS 1.3%
An issue was discovered in the stack_dst crate before 0.6.1 for Rust. Because of the push_inner behavior, a drop of uninitialized memory can occur upon a val.clone() panic.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.