Skip to content

Incorrect Handling of Non-Boolean Comparisons During Minification in uglify-js

Critical severity GitHub Reviewed Published Oct 24, 2017 to the GitHub Advisory Database • Updated Apr 12, 2023

Package

bundler uglifier (RubyGems)

Affected versions

< 2.7.2

Patched versions

2.7.2
npm uglify-js (npm)
< 2.4.24
2.4.24
Published by the National Vulnerability Database Jan 23, 2017
Published to the GitHub Advisory Database Oct 24, 2017
Reviewed Jun 16, 2020
Last updated Apr 12, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.794%
(82nd percentile)

CVE ID

CVE-2015-8857

GHSA ID

GHSA-34r7-q49f-h37c

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.