Incorrect Handling of Non-Boolean Comparisons During Minification in uglify-js
Versions of `uglify-js` prior to 2.4.24 are affected by a vulnerability which may cause crafted JavaScript to have altered functionality after minification. ## Recommendation Upgrade UglifyJS to version >= 2.4.24.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2015-8857US | critical9.8 | — | ||
The uglify-js package before 2.4.24 for Node.js does not properly account for non-boolean values when rewriting boolean expressions, which might allow attackers to bypass security… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2016/04/20/11WEB
- https://github.com/lautis/uglifier/commit/4677bfe38142937ff952f95605bcec4618892c3eWEB
- https://github.com/mishoo/UglifyJS2PACKAGE
- https://github.com/mishoo/UglifyJS2/issues/751WEB
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/uglifier/CVE-2015-8857.ymlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2015-8857ADVISORY
- https://web.archive.org/web/20200227190830/http://www.securityfocus.com/bid/96410WEB
- https://zyan.scripts.mit.edu/blog/backdooring-jsWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan