Skip to content

RUSTSEC-2020-0158

slice-deque is unmaintained

Not rated yet crates.io
Severity
Not rated yet
No source has published a CVSS score yet
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
—
Not classified
Fix
None yet
No fixed version published

Description

The author of the slice-deque crate is unresponsive and is not receiving security patches.

Maintained alternatives:

Affected versions

crates.io

PackageVulnerableFixed in
slice-deque
>= 0.0.0-0
No fix yet

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

References

Timeline

  1. Published
  2. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-7mcq-f592-pf7v
Slice Ring Buffer and Slice Deque contains four unique double-free vulnerabilities triggered through safe APIs
High Also affects slice-deque
GHSA-p9gf-gmfv-398m
Double free in slice-deque
High Also affects slice-deque
GHSA-c3m3-c39q-pv23
Out of bounds write in slice-deque
Critical Also affects slice-deque
GHSA-hr3c-6mmp-6m39
Memory corruption slice-deque
Critical Also affects slice-deque
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