Is CVE-2015-8858 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2015-8858 being exploited in the wild.

How severe is CVE-2015-8858?

High severity, with a CVSS score of 7.5, published 23 January 2017.

Which products and versions are affected?

uglify-js (npm) SEMVER:introduced=0,fixed=2.6.0.

Is there a fix for CVE-2015-8858?

Yes. uglify-js (npm): upgrade to 2.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2015-8858 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2015-8858?

Check whether you run uglify-js (npm) or Uglifyjs Project Uglifyjs 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.

CVE-2015-8858: UglifyJS ReDoS in parse call

CVE-2015-8858 · Severity: high · CVSS 7.5 · Published 2017-01-23

The uglify-js library, a popular tool for compressing and optimizing JavaScript code, is vulnerable to a denial-of-service attack. By providing specially crafted input to the parser, an attacker can cause the system to consume excessive CPU resources, potentially leading to application crashes or service outages. This affects developers and automated build systems that process untrusted JavaScript code.

Technologies: uglify-js (npm), Uglifyjs Project Uglifyjs. Vendors: npm, Uglifyjs Project.

Quick answers

Is CVE-2015-8858 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2015-8858 being exploited in the wild.
How severe is CVE-2015-8858?: High severity, with a CVSS score of 7.5, published 23 January 2017.
Which products and versions are affected?: uglify-js (npm) SEMVER:introduced=0,fixed=2.6.0.
Is there a fix for CVE-2015-8858?: Yes. uglify-js (npm): upgrade to 2.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2015-8858 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2015-8858?: Check whether you run uglify-js (npm) or Uglifyjs Project Uglifyjs 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

uglify-js (npm): upgrade to 2.6.0 or later
```
npm install uglify-js@2.6.0
```

Technical details

A Regular Expression Denial of Service (ReDoS) vulnerability exists in the uglify-js package before version 2.6.0. The flaw is located within the parsing logic, where certain crafted inputs trigger catastrophic backtracking in regular expression evaluation. This allows a remote, unauthenticated attacker to cause high CPU consumption and a denial-of-service condition by submitting malicious JavaScript code to be processed by the library. The issue is resolved in version 2.6.0.

Affected products

uglifyjs_project uglify-js < 2.6.0

Identifiers

CVE-2015-8858
GHSA-c9f4-xj24-8jqx

Timeline

2015-08-24: disclosed: Approximate date based on CVE assignment year and related advisories
2017-01-23: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.