Quick answers
- Is CVE-2015-8859 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2015-8859 being exploited in the wild.
- How severe is CVE-2015-8859?
- Medium severity, with a CVSS score of 5.3, published 23 January 2017.
- Which products and versions are affected?
- Send SEMVER:introduced=0,fixed=0.11.1.
- Is there a fix for CVE-2015-8859?
- Yes. Send: upgrade to 0.11.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2015-8859 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2015-8859?
- Check whether you run Send Project Send or Send at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Send: upgrade to 0.11.1 or later
Technical details
A path disclosure vulnerability exists in the 'send' package for Node.js in versions prior to 0.11.1. The flaw allows a remote, unauthenticated attacker to obtain the absolute root path of the application on the server's file system. This is typically classified as an information exposure vulnerability (CWE-200). While the specific exploitation vector is not detailed in the advisory, it is reachable over the network without prior authentication. The issue was addressed in version 0.11.1.
Affected products
- send_project send < 0.11.1
Identifiers
- CVE-2015-8859
- GHSA-jgqf-hwc5-hh37
Timeline
- 2015-08-01: disclosed: Approximate date based on CVE assignment year and related advisories
- 2017-01-23: advisory: NVD publication date