| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in uglify-js Package up to 2.4.23 on Node.js. This vulnerability affects unknown code. The manipulation leads to 7pk security. This vulnerability is listed as CVE-2015-8857. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.
Details
A vulnerability was found in uglify-js Package up to 2.4.23 on Node.js (JavaScript Library). It has been rated as critical. This issue affects an unknown code. The manipulation with an unknown input leads to a 7pk security vulnerability. Using CWE to declare the problem leads to CWE-254. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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 mechanisms or possibly have unspecified other impact by leveraging improperly rewritten Javascript.
The bug was discovered 08/24/2015. The weakness was presented 01/23/2017 (Website). The advisory is shared at openwall.com. The identification of this vulnerability is CVE-2015-8857 since 04/20/2016. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1211 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 518 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.4.24 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 96410†). See VDB-95801, VDB-95802, VDB-95803 and VDB-95804 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 2.4.0
- 2.4.1
- 2.4.2
- 2.4.3
- 2.4.4
- 2.4.5
- 2.4.6
- 2.4.7
- 2.4.8
- 2.4.9
- 2.4.10
- 2.4.11
- 2.4.12
- 2.4.13
- 2.4.14
- 2.4.15
- 2.4.16
- 2.4.17
- 2.4.18
- 2.4.19
- 2.4.20
- 2.4.21
- 2.4.22
- 2.4.23
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: 7pk securityCWE: CWE-254
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: uglify-js Package 2.4.24
Timeline
08/24/2015 🔍04/20/2016 🔍
01/23/2017 🔍
01/23/2017 🔍
01/23/2017 🔍
01/24/2017 🔍
05/14/2026 🔍
Sources
Advisory: openwall.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2015-8857 (🔍)
GCVE (CVE): GCVE-0-2015-8857
GCVE (VulDB): GCVE-100-95813
SecurityFocus: 96410 - Node.js uglify-js Package CVE-2015-8857 Security Bypass Vulnerability
OSVDB: - CVE-2015-8857 - Node.js - Security Bypass Issue
See also: 🔍
Entry
Created: 01/24/2017 08:29Updated: 05/14/2026 12:31
Changes: 01/24/2017 08:29 (60), 07/30/2020 12:46 (6), 05/14/2026 12:31 (19)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.