dbcve.org
Mystem WrapperApplication · Mystem Wrapper Project

CVE-2016-10671

HIGH · 8.1 CVSS v3.0 Published 2018-06-04
Fix available
A fix is available. Upgrade to after 0.2.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
mystem-wrapper is a Yandex mystem app wrapper module. mystem-wrapper downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested resources with an attacker controlled copy if the attacker is on the network or positioned in between the user and the remote server.

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

mstem-wrapper downloads binary resources over unencrypted HTTP, allowing network attackers to perform MITM attacks and replace legitimate binaries with malicious code, potentially achieving remote code execution on affected systems.

MitigationReplace HTTP URLs with HTTPS for all binary resource downloads and implement integrity verification (e.g., checksums or signatures) to ensure downloaded resources have not been tampered with.

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
Mystem WrapperApplication
Affected:<= 0.2.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. Check if mstem-wrapper is installed
    Run 'npm list mstem-wrapper' or check package.json for mstem-wrapper dependency
    Affected if mstem-wrapper is listed as a dependency in the project
  2. Determine installed version of mstem-wrapper
    Run 'npm list mstem-wrapper --depth=0' or check node_modules/mstem-wrapper/package.json for the version field
    Affected if The installed version is 0.2.0 or lower (any version <= 0.2.0)
  3. Inspect package source for binary download URLs
    Examine the package source code in node_modules/mstem-wrapper/ and search for HTTP URLs (http://) used to fetch binary resources
    Affected if Any binary resources are downloaded over unencrypted HTTP (http://) rather than HTTPS (https://)

The environment is affected if mstem-wrapper version 0.2.0 or lower is installed and the package fetches binary resources over HTTP URLs.

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 a release after 0.2.0
Interim mitigation

Replace HTTP URLs with HTTPS for all binary resource downloads and implement integrity verification (e.g., checksums or signatures) to ensure downloaded resources have not been tampered with.

Fix this in Mystem Wrapper Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10671 — 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-10671 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