Skip to content

slice-deque (crates.io)

Advisories
8
Latest version
—
License
—
OpenSSF Scorecard
—

How to fix

Upgrading to 0.2.0 or later clears every advisory below that has a fix.

Upgrade commands
cargo
cargo update -p slice-deque --precise 0.2.0

Known vulnerabilities

AdvisorySeverityAffectedFixed in
GHSA-7mcq-f592-pf7v
Slice Ring Buffer and Slice Deque contains four unique double-free vulnerabilities triggered through safe APIs
High
<= 0.3.0
No fix yet
GHSA-p9gf-gmfv-398m
Double free in slice-deque
High
EPSS 1.18%
<= 0.3.0
No fix yet
GHSA-p9gf-gmfv-398m
Double free in slice-deque
High
EPSS 1.18%
>= 0.0.0-0
No fix yet
RUSTSEC-2020-0158
slice-deque is unmaintained
Not rated yet
>= 0.0.0-0
No fix yet
GHSA-c3m3-c39q-pv23
Out of bounds write in slice-deque
Critical
EPSS 1.61%
>= 0.0.0-0, < 0.2.0
0.2.0
GHSA-c3m3-c39q-pv23
Out of bounds write in slice-deque
Critical
EPSS 1.61%
< 0.2.0
0.2.0
GHSA-hr3c-6mmp-6m39
Memory corruption slice-deque
Critical
EPSS 1.61%
>= 0.0.0-0, < 0.1.16
0.1.16
GHSA-hr3c-6mmp-6m39
Memory corruption slice-deque
Critical
EPSS 1.61%
< 0.1.16
0.1.16
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor