dbcve.org
Rust OpensslFramework / library · Rust Openssl Project

CVE-2016-10931

HIGH · 8.1 CVSS v3.0 Published 2019-08-26
Fix available
A fix is available. Upgrade to 0.9.0 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in the openssl crate before 0.9.0 for Rust. There is an SSL/TLS man-in-the-middle vulnerability because certificate verification is off by default and there is no API for hostname verification.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The openssl Rust crate before version 0.9.0 had SSL/TLS certificate verification disabled by default and lacked an API for hostname verification, allowing man-in-the-middle attackers to intercept encrypted communications by presenting fraudulent certificates.

MitigationUpgrade the openssl crate to version 0.9.0 or later and explicitly enable certificate and hostname verification in the application code.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rust OpensslFramework / library
Affected:< 0.9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate openssl crate dependency
    Search your project files (Cargo.toml, Cargo.lock) for the 'openssl' crate entry to confirm it is in use
    Affected if openssl crate is present in dependencies with version < 0.9.0
  2. Identify installed openssl version
    Run 'cargo tree -p openssl' or inspect Cargo.lock to find the resolved version of the openssl crate
    Affected if The resolved version is before 0.9.0 (e.g., 0.8.x, 0.7.x)
  3. Search for certificate verification configuration
    Search source code for SslVerifyMode, verify(), or set_verify() method calls on SSL builders
    Affected if No explicit verify mode is set, or SslVerifyMode::none() is used, leaving verification disabled by default
  4. Check for hostname verification API usage
    Search for HostNameType, add_host_application_layer_identification_random, or similar hostname verification methods in your TLS/SSL connection code
    Affected if No hostname verification is implemented (the 0.9.0 API was not available in earlier versions)

You are affected if your project uses the openssl Rust crate version 0.9.0 or earlier and does not explicitly enable both certificate and hostname verification in your SSL/TLS configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 0.9.0 or later
Fixed in 0.9.0
Interim mitigation

Upgrade the openssl crate to version 0.9.0 or later and explicitly enable certificate and hostname verification in the application code.

Fix this in Rust Openssl Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10931 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10931 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data