Quick answers
- Is CVE-2017-15881 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2017-15881 being exploited in the wild.
- How severe is CVE-2017-15881?
- Low severity, with a CVSS score of 3.1, published 16 November 2017.
- Which products and versions are affected?
- keystone (npm) SEMVER:introduced=0,fixed=4.0.0-beta7.
- Is there a fix for CVE-2017-15881?
- Yes. keystone (npm): upgrade to 4.0.0-beta7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2017-15881 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2017-15881?
- Check whether you run keystone (npm) 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
- keystone (npm): upgrade to 4.0.0-beta7 or later
npm install keystone@4.0.0-beta7
Technical details
KeystoneJS fails to properly encode rendered HTML in admin-created blog posts, resulting in a stored cross-site scripting (XSS) vulnerability (CWE-79). An attacker with administrative privileges can inject arbitrary JavaScript into blog post content. When other users view the compromised blog post, the malicious script executes in their browser with the privileges of their session. The attack requires admin-level account access and user interaction (victims must view the infected post). The vulnerability was fixed in version 4.0.0-beta7 and later.
Affected products
- KeystoneJS keystone < 4.0.0
Identifiers
- CVE-2017-15881
- GHSA-7cv6-gvx3-m54m
Timeline
- 2017-11-16: disclosed
- 2017: patched: Fixed in version 4.0.0-beta7