LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16133: goserv is an http server.

goserv is an http server. goserv 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 analysishigh

Security readout for executives and security teams

Plain-English summary

goserv is a Node.js HTTP server package with a directory traversal flaw. If it is used to serve files, an attacker may be able to access files outside the intended web directory. The supplied sources list all versions as affected and do not provide a confirmed fixed version.

Executive priority

Treat as high priority if goserv is internet-facing or present on systems with sensitive files. If inventory confirms no goserv usage, no further action is needed beyond documenting the negative finding.

Technical view

CVE-2017-16133 is a CWE-22 path traversal issue in the goserv node module. The reported behavior allows crafted URL path traversal to reach filesystem locations outside the intended served directory. The bundle provides no CVSS score, patch version, or detailed vendor remediation.

Likely exposure

Exposure is likely limited to applications or internal tools that directly depend on the goserv node module. Risk is highest where goserv is reachable by untrusted users or serves from hosts containing secrets, application code, credentials, or operational files.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. A public proof-of-concept reference and Node Security advisory are cited, so the issue was publicly documented, but exploitation in the wild is not established here.

Researcher notes

Evidence is sparse: affected product and class are clear, but CVSS, fixed versions, exploit maturity, and vendor mitigation details are absent. Validate dependency presence first, then focus on reachability and filesystem sensitivity.

Mitigation direction

  • Inventory projects for direct or transitive use of goserv.
  • Remove or replace goserv where it is still deployed.
  • Restrict network access to any exposed goserv instance.
  • Avoid serving from directories near secrets or operational files.
  • Check vendor or package registry guidance for any maintained fix.

Validation and detection

  • Review package manifests and lockfiles for goserv.
  • Confirm whether any runtime service starts goserv.
  • Map exposed goserv instances to internal or public access paths.
  • Test file-serving boundaries in a controlled environment only.
  • Verify secrets are not stored under served filesystem paths.
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-16133 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
HackerOnegoserv 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.