CVE-2016-10664
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 · uneditedmystem is a Node.js wrapper for MyStem morphology text analyzer by Yandex.ru mystem 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 binary with an attacker controlled binary 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 confidenceThe mystem npm package downloads Yandex MyStem binary resources over unencrypted HTTP instead of HTTPS, allowing network attackers to intercept and substitute malicious binaries via MITM attacks, potentially achieving remote code execution on victim systems.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if mystem npm package is installedRun 'npm list mystem' or check your package.json dependencies for the mystem packageAffected if The mystem package is listed as a dependency
-
Locate the package download codeExamine the mystem package source in node_modules/mystem (or globally installed path) - look for files that handle binary downloads, typically in the main entry point or a 'lib' or 'bin' folderAffected if The package source code exists in node_modules
-
Inspect download URLs for HTTP usageSearch the package source code for 'http://' URLs, particularly those pointing to Yandex or MyStem download endpoints (e.g., search for 'http://' strings in the download-related functions)Affected if The code contains unencrypted HTTP URLs for downloading binaries
-
Check network activity during package usageIf the package is used, use a network proxy or tcpdump to observe if HTTP (port 80) connections are made to Yandex/MyStem servers during binary downloadAffected if The package makes unencrypted HTTP requests to download binaries at runtime
-
Verify binary integrity checking is absentReview the package code for any SHA checksum verification, Subresource Integrity (SRI), or cryptographic signature validation before executing downloaded binariesAffected if No integrity verification mechanism is implemented before binary execution
A user is affected if the mystem npm package is installed and its code downloads MyStem binaries over unencrypted HTTP without integrity verification.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace HTTP download URLs with HTTPS and implement cryptographic integrity verification (e.g., SHA checksums or Subresource Integrity) for all downloaded binaries before execution.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10664 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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