rustsec/advisory-db
1
0
Fork 0
mirror of https://github.com/rustsec/advisory-db.git synced 2025-12-27 01:54:07 -05:00
Code Issues Packages Projects Releases Wiki Activity

DFs in slice-ring-buffer (#2336)

Browse Source
This commit is contained in:
George Androutsopoulos
2025-07-14 23:16:52 +03:00
committed by GitHub
parent 90cc845377
commit e9fe7f2228
1 changed files with 29 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
crates/slice-ring-buffer/RUSTSEC-0000-0000.md Normal file
View File

@@ -0,0 +1,29 @@
```toml
[advisory]
id = "RUSTSEC-0000-0000"
package = "slice-ring-buffer"
date = "2025-06-16"
url = "https://github.com/LiquidityC/slice_ring_buffer/issues/12"
categories = ["memory-corruption"]
keywords = ["memory-safety", "double-free"]
[affected.functions]
"slice_ring_buffer::SliceRingBuffer::extend_from_slice" = ["<= 0.3.4"]
"slice_ring_buffer::SliceRingBuffer::shrink_to_fit" = ["<= 0.3.4"]
"slice_ring_buffer::SliceRingBuffer::insert" = ["<= 0.3.4"]
"slice_ring_buffer::IntoIter::clone" = ["<= 0.3.4"]
[versions]
patched = []
```
# Four unique double-free vulnerabilities triggered via safe APIs
The crate [`slice-ring-buffer`](https://crates.io/crates/slice-ring-buffer) was developed as a fork of [`slice-deque`](https://crates.io/crates/slice-deque) to continue maintenance and provide security patches, since the latter has been officially unmaintained ([RUSTSEC-2020-0158](https://rustsec.org/advisories/RUSTSEC-2020-0158.html)).
While `slice-ring-buffer` has addressed some previously reported memory safety issues inherited from its fork origin ([RUSTSEC-2021-0047](https://rustsec.org/advisories/RUSTSEC-2021-0047.html)), it still retains multiple unresolved memory corruption vulnerabilities.
Specifically, we have discovered four new memory safety bugs, each resulting in double-free violations that can occur when only safe APIs are invoked. These vulnerabilities correspond to four distinct safe APIs in the crate, each exposing unsound and vulnerable behavior due to incorrect usage of unsafe code internally.
Unfortunately, the maintainer doesn't have much availability to resolve these issues so there's no concrete timeline for fixes. Community contributions towards fixing these vulnerabilities would be much appreciated.