LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10627: scala-bin is a binary wrapper for Scala.

scala-bin is a binary wrapper for Scala. scala-bin 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 analysishigh

Security readout for executives and security teams

Plain-English summary

scala-bin is a Node module wrapper for Scala that downloaded binary resources over plain HTTP. A network-positioned attacker could substitute the downloaded binary, potentially causing code execution on the installing or running system.

Executive priority

Prioritize removal where scala-bin appears in CI or developer setup paths, because compromise could affect build systems or workstations. No active exploitation is documented in the supplied sources.

Technical view

CVE-2016-10627 is a cleartext transport weakness in the scala-bin node module. Sources state all versions are affected. The risk is binary substitution during HTTP download, with possible RCE if an attacker can intercept or alter network traffic.

Likely exposure

Exposure is most likely in JavaScript projects, developer workstations, or CI systems that install or invoke the scala-bin node module. The source bundle does not identify affected Scala distributions beyond this package.

Exploitation context

The provided sources do not show known active exploitation, and KEV is false. Exploitation depends on attacker network position or another ability to tamper with the HTTP binary download path.

Researcher notes

Evidence is limited: no CVSS vector is provided, and the referenced advisory is the main technical source. Treat the impact as conditional RCE through MITM against HTTP binary retrieval, not a remotely reachable service flaw.

Mitigation direction

  • Inventory package manifests and lockfiles for scala-bin references.
  • Remove scala-bin or replace it with a vendor-recommended safe alternative.
  • Check current vendor or package guidance before choosing remediation.
  • Avoid workflows that execute binaries downloaded over plain HTTP.
  • Restrict package installation and CI egress to trusted networks.

Validation and detection

  • Confirm no production, CI, or developer project depends on scala-bin.
  • Review lockfiles for direct and transitive scala-bin entries.
  • Check CI logs for scala-bin installation or execution.
  • Verify remediation against vendor or package registry guidance.
  • Document any retained use and compensating network controls.
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-10627 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
HackerOnescala-bin 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.