LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10644: slimerjs-edge is a npm wrapper for installing the bleeding edge version of slimerjs.

slimerjs-edge is a npm wrapper for installing the bleeding edge version of slimerjs. slimerjs-edge 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2016-10644 affects the slimerjs-edge npm module. During installation, it downloads binary resources over unencrypted HTTP. Someone positioned on the network path could replace that binary and potentially run attacker-controlled code. This is mainly a software supply-chain and build-environment risk, not evidence of internet-wide exploitation.

Executive priority

Treat this as a targeted dependency hygiene issue. Prioritize confirmation in build and developer environments, then remove or replace the package if found. Do not treat it as an emergency unless the dependency is present in sensitive build pipelines.

Technical view

The issue is classified as CWE-311 because slimerjs-edge retrieves binary resources without transport encryption. The source bundle says all versions are affected and that a network-positioned attacker may swap the requested binary, potentially leading to RCE during installation or build workflows.

Likely exposure

Exposure is likely limited to projects, CI jobs, developer workstations, or build containers that install the slimerjs-edge node module. Organizations not using this package are not exposed based on the provided sources.

Exploitation context

The bundle does not show KEV listing or active exploitation. Exploitation requires an attacker on the network path or between the user and remote server during the HTTP binary download.

Researcher notes

The public bundle identifies insecure HTTP binary download behavior and possible RCE via binary substitution. It does not provide CVSS, exploit evidence, patch details, or proof of active exploitation. Avoid overstating impact beyond network-positioned tampering during installation.

Mitigation direction

  • Inventory projects and build systems for the slimerjs-edge npm module.
  • Remove or replace slimerjs-edge where business use is no longer required.
  • Check vendor or package-maintainer guidance before assuming a fixed version exists.
  • Avoid installing affected dependencies on untrusted networks.
  • Use controlled, trusted package and artifact sources for builds.

Validation and detection

  • Review package manifests and lockfiles for slimerjs-edge.
  • Check CI and developer build workflows that install npm dependencies.
  • Confirm whether any builds retrieve slimerjs-edge binary resources.
  • Document affected repositories, build agents, and owners.
  • Verify remediation by confirming the dependency is removed or vendor guidance is applied.
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-10644 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
HackerOneslimerjs-edge 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.