Quick answers
- Is CVE-2017-1000427 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2017-1000427 being exploited in the wild.
- How severe is CVE-2017-1000427?
- Low severity, with a CVSS score of 3, published 4 January 2018.
- Which products and versions are affected?
- marked (npm) SEMVER:introduced=0,fixed=0.3.7.
- Is there a fix for CVE-2017-1000427?
- Yes. marked (npm): upgrade to 0.3.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2017-1000427 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2017-1000427?
- Check whether you run marked (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
- marked (npm): upgrade to 0.3.7 or later
npm install marked@0.3.7
Technical details
The vulnerability is a cross-site scripting (XSS) flaw (CWE-79) in the data: URI parser component of Marked. Versions 0.3.6 and earlier fail to properly sanitize or neutralize user-controlled input within data URIs before rendering the output as HTML. An attacker can craft a Markdown document containing a malicious data URI in a link or image element that, when processed by Marked, executes arbitrary JavaScript in the context of the page. The attack requires user interaction (opening or viewing the crafted Markdown), but has network reach since Markdown can be served remotely. The fix is available in version 0.3.7 and later.
Affected products
- markedjs Marked <0.3.7
Identifiers
- CVE-2017-1000427
- GHSA-7px7-7xjx-hxm8
Timeline
- 2018-01-04: disclosed
- 2018-01-04: patched: Fixed in Marked 0.3.7