LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10676: rs-brightcove is a wrapper around brightcove's web api rs-brightcove downloads source file resources over H...

rs-brightcove is a wrapper around brightcove's web api rs-brightcove downloads source file 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

rs-brightcove downloaded source resources over plain HTTP. A network-positioned attacker could replace those resources in transit, potentially leading to remote code execution. The sources do not provide a CVSS score, confirmed exploitation, or a named fixed version.

Executive priority

Treat as a targeted dependency risk, not an internet-wide emergency. Prioritize review if rs-brightcove appears in production, CI, or deployment systems because the stated worst case is remote code execution.

Technical view

CVE-2016-10676 affects all versions of the rs-brightcove Node module. The issue is cleartext resource retrieval over HTTP, mapped to CWE-311. Impact depends on whether installs or runtime workflows fetch those resources while an attacker can intercept traffic.

Likely exposure

Exposure is likely limited to projects that depend on the rs-brightcove Node module and execute its resource-download path. Systems are most at risk when dependency installation or operation occurs on untrusted or interceptable networks.

Exploitation context

No source in the bundle reports active exploitation, and the CVE is not marked KEV. The described attack requires a man-in-the-middle position between the user and remote server, then tampering with HTTP-delivered resources.

Researcher notes

The public record is sparse: all versions are listed as affected, severity is unknown, and no patch details are provided in the bundle. Validation should focus on dependency presence, execution context, and whether HTTP resource retrieval is reachable.

Mitigation direction

  • Inventory applications and build pipelines for rs-brightcove usage.
  • Check vendor or advisory guidance for a fixed or recommended replacement package.
  • Avoid installing or running the dependency on untrusted networks.
  • Prefer removing the dependency if no maintained safe version is available.
  • Use dependency allowlisting and lockfiles to reduce unexpected package behavior.

Validation and detection

  • Review package manifests, lockfiles, and SBOMs for rs-brightcove.
  • Confirm whether any production or CI workflow invokes the affected resource download behavior.
  • Check whether installs occur only through trusted, monitored networks.
  • Record compensating controls if removal or replacement is delayed.
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-10676 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
HackerOners-brightcove 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.