LiveActive security incident?Get immediate response
CVE Record

CVE-2018-3712: serve node module before 6.4.9 suffers from a Path Traversal vulnerability due to not handling %2e (.) and...

serve node module before 6.4.9 suffers from a Path Traversal vulnerability due to not handling %2e (.) and %2f (/) and allowing them in paths, which allows a malicious user to view the contents of any directory with known path.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-3712 is a path traversal flaw in the Node.js serve module before 6.4.9. A remote user could request encoded path components and view directories at known paths, potentially exposing source, configuration, or other sensitive files if the server is reachable.

Executive priority

Prioritize remediation for internet-facing deployments or environments where serve runs near sensitive files. Treat as lower urgency for non-public development-only use, but still remove old versions because exploitation can expose data without authentication.

Technical view

The issue is CWE-22 path traversal. Affected serve versions mishandled encoded dot and slash characters in request paths, allowing traversal outside intended served paths and directory content disclosure. The bundle identifies versions before 6.4.9 as affected.

Likely exposure

Exposure is likely where applications or deployment tooling use the serve npm module before 6.4.9, especially for public static hosting. Impact depends on reachable paths and whether sensitive directories are accessible from the serving process.

Exploitation context

The source bundle does not identify CISA KEV listing or active exploitation. Public references include a HackerOne report and GitHub pull request, so the vulnerability details were publicly known after disclosure.

Researcher notes

Evidence is limited to the CVE description and linked public report/fix references. No CVSS score is provided in the bundle. Validate exposure by dependency version and deployment context rather than assuming every Node.js service is affected.

Mitigation direction

  • Upgrade the serve node module to version 6.4.9 or later.
  • Review vendor and project guidance for the exact fixed release and migration notes.
  • Avoid serving from directories that contain secrets, source repositories, or configuration files.
  • Restrict public access to affected static servers until upgraded.

Validation and detection

  • Inventory package manifests and lockfiles for serve versions before 6.4.9.
  • Confirm deployed runtime artifacts use the upgraded package, not only source files.
  • Review static serving roots for sensitive files or parent directory exposure.
  • Check web access logs for encoded traversal-looking requests around public endpoints.
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-3712 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
HackerOneserve node moduleVersions before 6.4.9Listed
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.