LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16130: exxxxxxxxxxx is an Http eX Frame Google Style JavaScript Guide.

exxxxxxxxxxx is an Http eX Frame Google Style JavaScript Guide. exxxxxxxxxxx is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing "../" in the url. Accessible files are restricted to those with a file extension. Files with no extension such as /etc/passwd throw an error.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2017-16130 affects the exxxxxxxxxxx npm module. A web request can use path traversal to read files from the server filesystem when those files have extensions. The sources do not provide a CVSS score, fixed version, or confirmed active exploitation.

Executive priority

Prioritize discovery first. The business risk depends on whether this old npm module is deployed in internet-facing services. If present, treat it as urgent to contain because filesystem reads can expose secrets, source files, or configuration.

Technical view

The issue is CWE-22 directory traversal in the HackerOne exxxxxxxxxxx node module, listed as affecting all versions. The CVE description says attackers can place traversal sequences in a URL to access filesystem paths, but files without extensions return an error. Evidence is limited to CVE data, a Node Security advisory reference, and a public PoC reference.

Likely exposure

Exposure is likely limited to applications that include this npm module and expose its HTTP file-handling behavior to untrusted users. The bundle does not show prevalence, package status, or whether the module is commonly deployed in production.

Exploitation context

The source bundle references a public proof-of-concept repository, but KEV is false and no cited source confirms active exploitation. Treat this as publicly documented technique availability, not evidence of exploitation in the wild.

Researcher notes

Do not assume full host compromise from the provided evidence. The described impact is file read via traversal, with an extension restriction. No CVSS vector, patch version, or exploit-in-the-wild signal is supplied, so conclusions should remain source-bounded.

Mitigation direction

  • Check the Node Security advisory and CVE record for vendor remediation guidance.
  • Inventory applications and lockfiles for the exxxxxxxxxxx npm module.
  • Do not expose affected functionality to untrusted users until remediation is confirmed.
  • Replace or remove the dependency if no fixed version is available.
  • Limit filesystem permissions for any service using the module.

Validation and detection

  • Search dependency manifests and lockfiles for exxxxxxxxxxx.
  • Confirm whether affected code handles public HTTP requests.
  • Review logs for suspicious traversal-like URL patterns.
  • Verify service accounts cannot read sensitive application or host files.
  • Record exposed services and remediation decisions.
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-16130 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
HackerOneexxxxxxxxxxx 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.