Quick answers
- Is CVE-2017-16114 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2017-16114 being exploited in the wild.
- How severe is CVE-2017-16114?
- Low severity, with a CVSS score of 3, published 24 July 2018.
- Which products and versions are affected?
- marked (npm) SEMVER:introduced=0,fixed=0.3.9.
- Is there a fix for CVE-2017-16114?
- Yes. marked (npm): upgrade to 0.3.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2017-16114 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2017-16114?
- 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.9 or later
npm install marked@0.3.9
Technical details
The vulnerability is a regular expression denial of service (ReDoS) vulnerability caused by inefficient pattern matching in marked's parser logic (CWE-400). The affected regular expression exhibits catastrophic backtracking when processing adversarial input, with documented amplification such that approximately 1,000 characters of malicious Markdown can block the Node.js event loop for around 6 seconds. The attack requires only network-level access to send malicious Markdown input—no authentication or user interaction beyond normal usage is required. An attacker can exploit this to cause denial of service against any application using vulnerable versions of marked. The vulnerability was fixed in version 0.3.9 and later.
Affected products
- marked marked before 0.3.9
Identifiers
- CVE-2017-16114
- GHSA-x5pg-88wf-qq4p
Timeline
- 2018-07-24: disclosed
- 2017: patched: Fix released in version 0.3.9