LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16145: sspa is a server dedicated to single-page apps.

sspa is a server dedicated to single-page apps. sspa 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

CVE-2017-16145 is a directory traversal flaw in the sspa Node.js module. A remote user may be able to request files outside the intended single-page app directory, potentially exposing sensitive server files. The source bundle lists all versions as affected, but does not provide CVSS, patch details, or confirmed active exploitation.

Executive priority

Prioritize inventory and replacement if sspa is deployed on exposed services. The business concern is unauthorized file disclosure, but the urgency is moderated by missing CVSS data and no confirmed active exploitation in the provided sources.

Technical view

The issue is CWE-22 in sspa, a server for single-page apps. The CVE description says placing parent-directory traversal sequences in the URL can provide filesystem access. Affected scope is listed as all versions of the HackerOne sspa node module. Available sources do not define authentication requirements, file-read boundaries, or fixed versions.

Likely exposure

Exposure is most likely where sspa is used to serve a public or internal single-page application. Systems not using the sspa Node.js module are not indicated as affected by the provided sources.

Exploitation context

CISA KEV status is false in the bundle, so active exploitation is not established. A public proof-of-concept reference is listed, which raises validation urgency, but the provided evidence does not prove real-world exploitation.

Researcher notes

Evidence is sparse. The CVE states filesystem access through URL traversal and lists all versions affected. No patch, vulnerable code details, authentication model, or impact limits are provided in the bundle, so validation should focus on confirmed dependency presence and reachable request handling.

Mitigation direction

  • Identify whether any deployed service depends on the sspa Node.js module.
  • Check vendor or package-maintainer guidance for fixed versions or replacement recommendations.
  • Remove or replace sspa where no supported fix is available.
  • Restrict direct exposure of affected services where replacement cannot be immediate.
  • Review logs for suspicious traversal-style URL requests.

Validation and detection

  • Search application dependency manifests and lockfiles for sspa.
  • Map any sspa usage to running services and exposed routes.
  • Confirm whether sspa handles untrusted HTTP request paths.
  • Review package advisory sources for fixed-version information.
  • Check web logs for requests attempting directory traversal patterns.
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-16145 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
HackerOnesspa 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.