LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16121: datachannel-client is a signaling implementation for DataChannel.js.

datachannel-client is a signaling implementation for DataChannel.js. datachannel-client is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing "../" in the url.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2017-16121 affects the datachannel-client Node module, a signaling component for DataChannel.js. The sources describe a directory traversal flaw that can let an attacker access filesystem paths by abusing URL path handling. Severity, CVSS, fixed version, and vendor mitigation details are not provided in the bundle.

Executive priority

Prioritize inventory and containment over emergency response. The issue can expose filesystem data, but the provided sources lack severity scoring, fixed-version guidance, and active exploitation evidence. Escalate quickly if the module is internet-facing or protects sensitive files.

Technical view

The vulnerability is classified as CWE-22. The affected package is listed as datachannel-client, all versions. The described issue is insufficient path traversal control in URL handling, allowing filesystem access through parent-directory path elements. No CVSS vector, patch level, or supported remediation path is included in the provided sources.

Likely exposure

Exposure is most likely in Node.js applications that still include the datachannel-client module and expose the vulnerable signaling functionality to untrusted URL input. The bundle does not identify downstream products, package usage patterns, or vulnerable deployment configurations beyond the module itself.

Exploitation context

The bundle includes a public proof-of-concept reference, but KEV is false and no cited source states active exploitation. Treat exploitation status as unconfirmed. The available evidence supports vulnerability existence, not current attack activity or prevalence.

Researcher notes

Evidence is concise and incomplete. The CVE description, CWE-22 classification, all-versions affected statement, and PoC reference are clear. Missing data includes CVSS, affected commit range, fixed release, exploit maturity beyond a PoC, and vendor-endorsed remediation.

Mitigation direction

  • Inventory applications for the datachannel-client Node module.
  • Check vendor and npm advisory sources for current remediation guidance.
  • Remove or replace the module if it remains in use and no safe version exists.
  • Limit external access to services depending on this module.
  • Review logs for suspicious path traversal attempts against affected routes.

Validation and detection

  • Search dependency manifests and lockfiles for datachannel-client.
  • Confirm whether affected code paths accept untrusted URL input.
  • Map any exposed services using the vulnerable module.
  • Document whether the package remains reachable in production.
  • Track advisory updates because the bundle names no fixed version.
Prepared
Confidence
medium
Sources
4

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 · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. 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-2017-16121 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
3Source links

CVSS and timeline data

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

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HackerOnedatachannel-client 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-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.