LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16169: looppake is a simple http server.

looppake is a simple http server. looppake 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

CVE-2017-16169 is a directory traversal flaw in the looppake Node module, described as a simple HTTP server. A crafted URL can let an attacker access files outside the intended web directory. Sources list all versions as affected, but do not provide CVSS, active exploitation, or a fixed version.

Executive priority

Prioritize inventory and removal if looppake is internet-facing or handles sensitive files. Business urgency depends on actual deployment, but the potential impact is unauthorized filesystem access and the sources do not name a patch.

Technical view

The issue is CWE-22 path traversal in looppake. The public CVE description says filesystem access is possible when parent-directory traversal is placed in a URL. The source bundle identifies all versions of the looppake node module as affected and includes a public proof-of-concept reference, but no detailed remediation or exploit-in-the-wild evidence.

Likely exposure

Exposure is limited to systems that install and run the looppake Node module as an HTTP server, especially if reachable by untrusted users. The source bundle does not establish prevalence, default exposure, or transitive dependency risk.

Exploitation context

CISA KEV status is false, and the provided sources do not claim active exploitation. A public proof-of-concept reference exists, so defenders should treat reachable deployments as realistically testable by attackers, without assuming exploitation is occurring.

Researcher notes

Evidence is sparse: CVE text, CWE-22 classification, all-versions affected statement, advisory reference, and public PoC reference. Do not infer affected forks, package popularity, or exploit activity from the bundle alone.

Mitigation direction

  • Inventory applications, containers, and lockfiles for the looppake Node module.
  • Remove or replace looppake where feasible; sources do not identify a fixed version.
  • Restrict any looppake server from untrusted networks until vendor guidance is confirmed.
  • Review the Node Security advisory and package repository for remediation status.
  • Add detection for unexpected file access attempts in exposed HTTP services.

Validation and detection

  • Check dependency manifests and lockfiles for looppake.
  • Confirm whether any looppake-based HTTP server is reachable by external users.
  • Review web server logs for suspicious path traversal patterns.
  • Verify application file-serving logic confines requests to the intended directory.
  • Document compensating controls if replacement is not immediately possible.
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-16169 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
HackerOnelooppake 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.