LiveActive security incident?Get immediate response
CVE Record

CVE-2018-3715: glance node module before 3.0.4 suffers from a Path Traversal vulnerability due to lack of validation of pa...

glance node module before 3.0.4 suffers from a Path Traversal vulnerability due to lack of validation of path passed to it, which allows a malicious user to read content of any file with known path.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-3715 is a path traversal flaw in the glance Node.js module before 3.0.4. If an application lets an untrusted user influence paths passed to glance, that user may be able to read files at known paths. Business risk depends on whether glance is present and reachable in deployed services.

Executive priority

Prioritize remediation for internet-facing or multi-tenant Node.js services using glance. The issue can expose sensitive local files, but urgency should be driven by confirmed dependency presence and user-controlled reachability.

Technical view

The CVE describes CWE-22 in glance before 3.0.4: insufficient validation of a path argument allows reading arbitrary files with known paths. The source bundle identifies 3.0.4 as the fixed boundary and links to the upstream commit. No CVSS score is provided.

Likely exposure

Exposure is most likely in Node.js applications that directly or transitively depend on glance versions before 3.0.4 and pass user-controlled path values into it. Internal-only tools may still be exposed if reachable by untrusted users or tenants.

Exploitation context

The source bundle does not cite KEV listing or active exploitation. It supports a file-read impact, not code execution. Practical exploitation depends on application routing, path handling, filesystem permissions, and whether an attacker can predict sensitive file locations.

Researcher notes

Evidence is limited to the CVE description, HackerOne report, and upstream commit reference. No CVSS vector, affected CPEs, or exploitation-in-the-wild evidence is provided. Treat risk assessment as deployment-dependent and validate data flow before escalating.

Mitigation direction

  • Upgrade glance to version 3.0.4 or later.
  • Check direct and transitive dependencies for vulnerable glance versions.
  • Avoid passing untrusted path input to glance.
  • Apply strict allowlists for permitted file roots and names.
  • Review vendor and upstream guidance before relying on compensating controls.

Validation and detection

  • Inspect package lockfiles and SBOMs for glance below 3.0.4.
  • Map application code paths that call glance with request-derived input.
  • Confirm deployed artifacts use the remediated dependency version.
  • Test path validation with non-sensitive fixtures only.
  • Review logs for suspicious file-read attempts or path errors.
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-2018-3715 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HackerOneglance node moduleVersions before 3.0.4Listed
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.