Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 31 July 2018.
- Which products and versions are affected?
- moment (npm) SEMVER:introduced=0,fixed=2.11.2.
- Is there a fix for This vulnerability?
- Yes. moment (npm): upgrade to 2.11.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run moment (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
- moment (npm): upgrade to 2.11.2 or later
npm install moment@2.11.2
Technical details
This vulnerability is a Regular Expression Denial of Service (ReDoS) flaw in the duration function of moment.js. The vulnerable component uses a regex pattern that exhibits exponential backtracking behavior when processing certain input strings, allowing an attacker to craft long strings that trigger excessive CPU consumption. The attack vector is network-based and requires no authentication—any application accepting untrusted input and passing it to the duration function is at risk. The vulnerability affects versions before 2.11.2, which includes a fix for the problematic regex pattern. This advisory was withdrawn as an accidental duplicate of CVE-2016-4055.
Affected products
- Moment.js Moment before 2.11.2
Timeline
- 2018-07-31: disclosed: Advisory published to GitHub Advisory Database
- 2011-02-01: patched: Fixed in version 2.11.2
- 2020-06-17: other: Advisory withdrawn as accidental duplicate of CVE-2016-4055