LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16131: unicorn-list is a web framework.

unicorn-list is a web framework. unicorn-list 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-16131 describes a directory traversal flaw in the unicorn-list Node.js web framework. A crafted URL using parent-directory traversal can give an attacker filesystem access outside the intended web path. The source bundle lists all versions as affected, but provides no CVSS score or named fixed version.

Executive priority

Prioritize discovery first because severity and fixed-version data are incomplete. Escalate quickly if unicorn-list is present in an internet-facing service, because directory traversal can expose sensitive files and application secrets.

Technical view

The flaw is classified as CWE-22. The vulnerable behavior is URL path handling that permits ../ traversal and can expose filesystem contents. Evidence identifies the affected package as the unicorn-list node module across all versions. No patch, configuration mitigation, or exploitation-in-the-wild evidence is provided in the bundle.

Likely exposure

Exposure is likely limited to applications that directly depend on unicorn-list and expose its file-serving or routing behavior to untrusted HTTP requests. Organizations not using this Node.js module are not affected based on the supplied evidence.

Exploitation context

The bundle includes a public proof-of-concept reference, but KEV is false and no cited source states active exploitation. Treat the issue as publicly known, not confirmed as exploited in the wild.

Researcher notes

Do not assume a vendor patch from the provided data. Validate dependency presence, exposed request paths, and filesystem access boundaries. The GitHub reference indicates public PoC material exists, but this assessment does not rely on exploit details.

Mitigation direction

  • Inventory applications and lockfiles for the unicorn-list node module.
  • Check the Node Security advisory and vendor guidance for any fixed release or workaround.
  • Remove or replace unicorn-list where internet-facing exposure exists.
  • Restrict public access to affected services until remediation is confirmed.
  • Review application file-serving controls for traversal-resistant path handling.

Validation and detection

  • Search package manifests and dependency lockfiles for unicorn-list.
  • Confirm whether any running service exposes unicorn-list routes to untrusted users.
  • Review web logs for suspicious traversal-style URL paths.
  • Verify file-serving tests reject parent-directory traversal paths.
  • Document findings, affected services, and compensating controls.
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-16131 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HackerOneunicorn-list 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.