CVE-2019-15543: Slice deque Out Of Bounds Write Vulnerability

CRITICAL
Advisory Identifier: GHSA-c3m3-c39q-pv23
Share
CVSS 9.8
CWE-787
Published
Advisory Summary

CVE-2019-15543 is a CRITICAL (CVSS 9.8) out of bounds write vulnerability (CWE-787: Out-of-bounds Write) affecting Slice deque libraries in the crates.io ecosystem. The issue involves out of bounds write in slice-deque. Remediation is available by upgrading affected packages to version 0.2.0.

CVE-2019-15543 at a Glance

CVE Identifier CVE-2019-15543
GHSA Identifier GHSA-c3m3-c39q-pv23
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-787: Out-of-bounds Write
Affected Product Slice deque
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2019-15543

To remediate this vulnerability, upgrade all affected Slice deque dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

slice-deque fixed: 0.2.0 
Upgrade slice-deque to 0.2.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for slice-deque

How to Check if You Are Affected

To determine whether your application is affected by CVE-2019-15543, inspect your project dependencies for Slice deque:

inspect dependencies for slice-deque

Analyze the terminal output to locate any version of Slice deque in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.2.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-787: Out-of-bounds Write, where the product writes data past the end, or before the beginning, of the intended buffer. In Slice deque, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Affected versions of this crate entered a corrupted state if mem::size_of::<T>() % allocation_granularity() != 0 and a specific allocation pattern was used: sufficiently shifting the deque elements over the mirrored page boundary. This allows an attacker that controls controls both element insertion and removal to corrupt the deque, such that reading elements from it would read bytes corresponding to other elements in the deque. (e.g. a read of T could read some bytes from one value and some bytes from an adjacent one, resulting in a T whose value representation is not meaningful). This is undefined behavior. The flaw was corrected by using a pair of pointers to track the head and tail of the deque instead of a pair of indices. This pair of pointers are represented using a Rust slice.

CVE-2019-15543 Affected Slice deque Versions

1 component(s)
Fixed Versions:
0.2.0
Product / Package Ecosystem Affected Versions Fixed Version
slice-deque
 crates.io
< 0.2.0
0.2.0

References

NVD — CVE-2019-15543 NVD
https://nvd.nist.gov/vuln/detail/CVE-2019-15543
Slice deque Source Repository REPOSITORY
https://github.com/gnzlbg/slice_deque/issues/57
Slice deque Source Repository REPOSITORY
https://github.com/gnzlbg/slice_deque
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2019-0002.html

Frequently Asked Questions

What is CVE-2019-15543?
CVE-2019-15543 is a security vulnerability in Slice deque involving Out of bounds write in slice-deque under CWE-787: Out-of-bounds Write.
Which Slice deque versions are affected?
Affected versions include releases prior to 0.2.0 across affected packages: slice-deque.
What version fixes CVE-2019-15543?
Upgrading to 0.2.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is slice-deque affected?
Yes, slice-deque is affected in releases prior to 0.2.0. Upgrade your dependency to 0.2.0 or later.
What is the CVSS score of CVE-2019-15543?
CVE-2019-15543 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2019-15543?
CVE-2019-15543 is classified under CWE-787: Out-of-bounds Write (The product writes data past the end, or before the beginning, of the intended buffer.).
How can I check crates.io dependencies for CVE-2019-15543?
Run the dependency tree command: 'inspect dependencies for slice-deque'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-c3m3-c39q-pv23",
  "modified" : "2023-06-13T20:56:39Z",
  "published" : "2021-08-25T20:44:10Z",
  "aliases" : [ "CVE-2019-15543" ],
  "summary" : "Out of bounds write in slice-deque",
  "details" : "Affected versions of this crate entered a corrupted state if mem::size_of::<T>() % allocation_granularity() != 0 and a specific allocation pattern was used: sufficiently shifting the deque elements over the mirrored page boundary.\n\nThis allows an attacker that controls controls both element insertion and removal to corrupt the deque, such that reading elements from it would read bytes corresponding to other elements in the deque. (e.g. a read of T could read some bytes from one value and some bytes from an adjacent one, resulting in a T whose value representation is not meaningful). This is undefined behavior.\n\nThe flaw was corrected by using a pair of pointers to track the head and tail of the deque instead of a pair of indices. This pair of pointers are represented using a Rust slice.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "slice-deque"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.2.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2019-15543"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/gnzlbg/slice_deque/issues/57"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/gnzlbg/slice_deque"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2019-0002.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-787" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-08-19T21:23:28Z",
    "nvd_published_at" : null
  }
}