CVE-2019-16137: RUSTSEC-2019-0013 - Wrong memory orderings in RwLock potentially violates mutual exclusion

CVE-2019-16137 · Severity: low · CVSS 3.1 · Published 2019-08-27

Wrong memory orderings in RwLock potentially violates mutual exclusion

Technologies: spin (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2019-16137 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-16137 being exploited in the wild.
How severe is CVE-2019-16137?
Low severity, with a CVSS score of 3.1, published 27 August 2019.
Which products and versions are affected?
spin (crates.io) SEMVER:introduced=0,fixed=0.5.2, SEMVER:introduced=0.0.0-0,fixed=0.5.2.
Is there a fix for CVE-2019-16137?
Yes. spin (crates.io): upgrade to 0.5.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-16137?
Check whether you run spin (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • spin (crates.io): upgrade to 0.5.2 or later
    cargo update -p spin

Affected products

  • spin (crates.io) SEMVER:introduced=0,fixed=0.5.2, SEMVER:introduced=0.0.0-0,fixed=0.5.2

Identifiers

  • CVE-2019-16137
  • GHSA-hv7x-f3pv-gpwr
  • RUSTSEC-2019-0013

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.