LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16201: zjjserver is a static file server.

zjjserver is a static file server. zjjserver 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

zjjserver, a Node.js static file server module, is reported vulnerable to directory traversal. An attacker could request paths that escape the intended web directory and read files from the host filesystem. The source bundle lists all versions as affected, but provides no CVSS score, patch version, or confirmed exploitation evidence.

Executive priority

Prioritize investigation if zjjserver is present on any public or partner-facing service. The likely business impact is unauthorized file disclosure, potentially including configuration or secrets. Because source data lacks severity scoring and remediation detail, first confirm exposure, then replace or isolate affected deployments.

Technical view

CVE-2017-16201 is a CWE-22 path traversal issue in the zjjserver node module. The CVE description says filesystem access is possible by placing parent-directory traversal sequences in the URL. Scope and reachable files depend on how the server process is deployed and what filesystem permissions it has.

Likely exposure

Exposure is likely only where applications directly or transitively use zjjserver to serve static files, especially if reachable from untrusted networks. The bundle lists all versions as affected, but does not describe package popularity, default deployment patterns, or a fixed release.

Exploitation context

The provided bundle includes a public proof-of-concept reference and a Node Security advisory reference. CISA KEV status is false, and the bundle gives no cited evidence of active exploitation in the wild. Treat internet-facing deployments as higher concern because the bug affects file access boundaries.

Researcher notes

Evidence is limited to the CVE record, CVE List data, a public PoC reference, and Node Security advisory reference. The affected entry says all versions of the zjjserver node module. No CVSS vector, patched version, exploit-in-the-wild claim, or detailed vendor mitigation is present in the supplied bundle.

Mitigation direction

  • Inventory direct and transitive use of the zjjserver node module.
  • Remove or replace zjjserver where feasible, especially on public-facing services.
  • Check upstream npm, vendor, or advisory guidance for any fixed version.
  • Restrict network exposure for any service still using zjjserver.
  • Run the service with least-privilege filesystem permissions.
  • Avoid storing secrets readable by the static file server process.

Validation and detection

  • Search dependency manifests and lockfiles for zjjserver.
  • Map any route or service that uses zjjserver for static file serving.
  • Review web logs for suspicious path traversal request patterns.
  • Confirm the server process cannot read sensitive host files.
  • Use authorized staging tests to verify static serving stays inside the intended root.
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-16201 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
HackerOnezjjserver 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.