Quick answers
- Is CVE-2015-1370 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2015-1370 being exploited in the wild.
- How severe is CVE-2015-1370?
- Informational severity, with a CVSS score of 6.1, published 24 October 2017.
- Which products and versions are affected?
- marked (npm) SEMVER:introduced=0,fixed=0.3.3.
- Is there a fix for CVE-2015-1370?
- Yes. marked (npm): upgrade to 0.3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2015-1370 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2015-1370?
- 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.3 or later
npm install marked@0.3.3
Technical details
The vulnerability is a cross-site scripting (CWE-79) flaw in marked's link sanitization logic. Affected versions 0.3.2 and earlier fail to properly strip or escape VBScript protocol handlers (vbscript:) in href attributes even when the sanitize option is set to true. An attacker can craft Markdown input containing [text](vbscript:alert(1)) which renders as a malicious link. The attack is browser-specific, most reliably exploitable in IE10 Compatibility Mode and potentially other Internet Explorer versions. The fix was released in version 0.3.3.
Affected products
- marked marked 0.3.2 and earlier
Identifiers
- CVE-2015-1370
- GHSA-cfjh-p3g4-3q2f
Timeline
- 2015-01: disclosed: Vulnerability reported and fixed in marked 0.3.3
- 2017-10-24: advisory: GHSA-cfjh-p3g4-3q2f published