LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10600: webrtc-native uses WebRTC from chromium project.

webrtc-native uses WebRTC from chromium project. webrtc-native 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
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2016-10600 is a supply-chain transport weakness in the webrtc-native Node module. It fetched binary resources over unencrypted HTTP, so someone positioned on the network could tamper with the download and potentially cause code execution. The sources do not show confirmed exploitation or a named patch.

Executive priority

Prioritize if webrtc-native appears in production builds, desktop apps, or CI pipelines. The main business risk is compromise during software build or installation, not routine web traffic. If the dependency is absent, no action is needed beyond documentation.

Technical view

webrtc-native uses WebRTC from Chromium and downloads binary resources over HTTP. The reported risk is MITM substitution of the requested binary with attacker-controlled content, potentially leading to RCE. The bundle lists all versions of the webrtc-native node module as affected and maps the issue to CWE-311.

Likely exposure

Exposure is likely limited to environments that use the webrtc-native Node module directly or through dependencies. The highest-risk point is dependency installation or build-time binary retrieval on untrusted networks, intercepted corporate proxies, or CI systems without trusted artifact controls.

Exploitation context

Active exploitation is not established. The source bundle says KEV is false and provides no cited evidence of exploitation in the wild. Exploitation would require network position between the user or build system and the HTTP download source.

Researcher notes

Evidence is sparse: no CVSS vector, no exploit confirmation, and no specific fixed version in the provided bundle. Treat the RCE impact as conditional on successful MITM binary substitution during HTTP retrieval, and avoid assuming broader WebRTC or Chromium exposure.

Mitigation direction

  • Inventory applications and lockfiles for the webrtc-native Node module.
  • Check the Node Security advisory or vendor guidance for supported remediation.
  • Remove or replace the dependency if no maintained fixed version is available.
  • Run dependency installs only from trusted networks and controlled CI environments.
  • Use trusted artifact sources and integrity controls for build dependencies.

Validation and detection

  • Search dependency manifests and lockfiles for webrtc-native.
  • Review CI and build logs for webrtc-native binary downloads over HTTP.
  • Confirm whether any transitive dependency pulls in webrtc-native.
  • Verify build environments enforce trusted dependency and artifact retrieval.
  • Document exposure decisions for systems where removal is not immediately feasible.
Prepared
Confidence
medium
Sources
3

Public sources used

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-10600 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
HackerOnewebrtc-native node moduleAll versionsListed
Weakness

CWE details

CWE-311

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.

Open CWE intelligenceSame-CWE CVEs