LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16106: tmock is a static file server.

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

tmock, a Node.js static file server, can let an attacker read files outside the intended web directory through directory traversal. For leaders, the concern is unauthorized disclosure of local files if this package is exposed to untrusted users. The sources do not provide a CVSS score or a fixed version.

Executive priority

Treat this as a targeted exposure check, not an organization-wide emergency by default. Prioritize any public-facing or partner-facing service using tmock because successful exploitation could disclose local files.

Technical view

CVE-2017-16106 is a CWE-22 directory traversal issue in the tmock npm module. The source description says crafted URLs containing parent-directory traversal can give filesystem access. The affected listing says all versions of the tmock node module are affected. No CVSS vector, patch version, or vendor remediation detail is included in the provided bundle.

Likely exposure

Exposure is likely limited to systems that install and actively use tmock to serve static files, especially if reachable by external or untrusted users. The bundle does not identify downstream applications, default deployment patterns, or internet-wide exposure.

Exploitation context

CISA KEV status is false in the bundle, so active exploitation is not evidenced here. The references include a public proof-of-concept repository, indicating vulnerability knowledge is public, but the bundle does not establish real-world exploitation.

Researcher notes

Evidence is sparse: affected versions are listed as all versions, severity is unknown, and no patch is named. Validate usage context before assigning priority. Avoid assuming exploit prevalence beyond the listed public PoC reference.

Mitigation direction

  • Inventory applications and tooling for the tmock npm package.
  • Remove or replace tmock where feasible; no fixed version is listed.
  • Keep any unavoidable use away from untrusted networks.
  • Restrict access to services using tmock with authentication or network controls.
  • Check vendor and advisory sources for remediation guidance.

Validation and detection

  • Review dependency manifests and lockfiles for tmock usage.
  • Confirm whether tmock-backed services are reachable by untrusted users.
  • Review application logs for suspicious traversal-like path requests.
  • Verify static file serving cannot access files outside intended roots.
  • Document findings because the source bundle lacks patch details.
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-16106 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
HackerOnetmock 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.