CVE-2016-10931: RUSTSEC-2016-0001 - SSL/TLS MitM vulnerability due to insecure defaults

CVE-2016-10931 · Severity: low · CVSS 3 · Published 2016-11-05

SSL/TLS MitM vulnerability due to insecure defaults

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

Quick answers

Is CVE-2016-10931 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2016-10931 being exploited in the wild.
How severe is CVE-2016-10931?
Low severity, with a CVSS score of 3, published 5 November 2016.
Which products and versions are affected?
openssl (crates.io) SEMVER:introduced=0,fixed=0.9.0, SEMVER:introduced=0.0.0-0,fixed=0.9.0.
Is there a fix for CVE-2016-10931?
Yes. openssl (crates.io): upgrade to 0.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2016-10931?
Check whether you run openssl (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

  • openssl (crates.io): upgrade to 0.9.0 or later
    cargo update -p openssl

Affected products

  • openssl (crates.io) SEMVER:introduced=0,fixed=0.9.0, SEMVER:introduced=0.0.0-0,fixed=0.9.0

Identifiers

  • CVE-2016-10931
  • GHSA-34p9-f4q3-c4r7
  • RUSTSEC-2016-0001

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