Security readout for executives and security teams
Plain-English summary
Restafary versions before 1.6.1 may fail to keep file API operations confined to the configured root directory. If exposed, users could interact with server files outside the intended area. Business risk depends on reachability, permissions, and what files the service account can access.
Executive priority
Prioritize review if restafary is internet-facing or handles sensitive filesystem locations. With no CVSS or KEV evidence in the bundle, broad emergency action is not supported, but affected deployments should upgrade promptly.
Technical view
CVE-2016-10528 is a CWE-22 issue in the HackerOne restafary node module before 1.6.1. Restafary provides REST-style file operations, and vulnerable versions do not reliably enforce the configured root path boundary. Sources provide no CVSS vector, exploit details, or concrete file impact.
Likely exposure
Exposure is likely limited to Node.js applications that depend on restafary before 1.6.1 and expose its file-management API. Risk is higher if reachable by untrusted users or running with broad filesystem permissions.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV in the bundle. No public exploit mechanics are cited here. Treat this as a boundary-control flaw requiring dependency and deployment review.
Researcher notes
The source bundle is sparse: it identifies product, affected version range, CWE-22, and the root-path confinement issue, but omits CVSS, patch notes, proof-of-concept status, and detailed impact boundaries. Validate exposure from application usage, not package presence alone.
Mitigation direction
- Upgrade restafary to version 1.6.1 or later where used.
- Check vendor advisory guidance before applying compensating controls.
- Restrict API access to trusted users and networks.
- Run the service with least-privilege filesystem permissions.
Validation and detection
- Inventory package manifests and lockfiles for restafary versions below 1.6.1.
- Confirm whether any deployed service exposes restafary routes externally.
- Review runtime permissions for the service account hosting restafary.
- Check dependency scanning results for CVE-2016-10528 coverage.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2016-10528 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://nodesecurity.io/advisories/89CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.