LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10666: tomita-parser is a Node wrapper for Yandex Tomita Parser tomita-parser downloads binary resources over HTTP...

tomita-parser is a Node wrapper for Yandex Tomita Parser tomita-parser 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects the tomita-parser Node module. It downloads binary resources over plain HTTP, so someone positioned on the network could replace the download. The public record says this may lead to remote code execution, but provides no CVSS score, patch details, or evidence of active exploitation.

Executive priority

Prioritize review if this package appears in active products, CI pipelines, or developer environments. The business risk is supply-chain compromise through an insecure binary download, with possible code execution. If absent from dependency inventories, no further action is indicated from the supplied sources.

Technical view

CVE-2016-10666 is an insecure transport issue in all versions of the HackerOne tomita-parser Node wrapper for Yandex Tomita Parser. The module retrieves binary resources over HTTP, creating a man-in-the-middle substitution risk. The source maps this to CWE-311 and describes possible RCE if attacker-controlled resources are substituted.

Likely exposure

Exposure exists where applications, CI systems, or developer workstations install or use the tomita-parser Node module and allow its HTTP resource download path. The source says all versions are affected. Organizations without this dependency are not exposed based on the provided evidence.

Exploitation context

The source describes a network-positioned attacker or intermediary swapping requested HTTP resources. There is no KEV listing and no provided source evidence of active exploitation, public exploit use, or observed campaigns. The attack depends on the vulnerable download behavior being reachable.

Researcher notes

The record is sparse: no CVSS vector, no patch version, and no current exploit evidence are provided. The key facts are all-version impact, HTTP binary retrieval, MITM precondition, CWE-311 classification, and possible RCE from attacker-controlled resource substitution.

Mitigation direction

  • Inventory JavaScript projects for the tomita-parser Node module.
  • Remove or replace the dependency where feasible.
  • Check vendor or package-maintainer guidance for fixed versions or safe configuration.
  • Avoid builds or installs over untrusted networks until resolved.
  • Pin and verify third-party binaries through trusted distribution paths.

Validation and detection

  • Search package manifests and lockfiles for tomita-parser.
  • Confirm whether any current build process downloads its binary resources.
  • Review CI and developer environments for historical dependency use.
  • Check dependency scanners for CVE-2016-10666 coverage.
  • Document any accepted risk if the dependency cannot be removed.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-311: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-10666 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HackerOnetomita-parser node moduleAll versionsListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-311 · source CWE mapping

Missing Encryption of Sensitive Data

Missing Encryption of Sensitive Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.