assign-deep up to 0.4.6 on Node.js Object access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in assign-deep up to 0.4.6 on Node.js. It has been declared as critical. The affected element is an unknown function. The manipulation as part of Object results in access control. This vulnerability is reported as CVE-2018-3720. The attack can be launched remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in assign-deep up to 0.4.6 on Node.js (JavaScript Library). It has been classified as critical. Affected is some unknown processing. The manipulation as part of a Object leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
assign-deep node module before 0.4.7 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects.
The bug was discovered 04/25/2018. The weakness was disclosed 06/07/2018 (Website). The advisory is available at github.com. This vulnerability is traded as CVE-2018-3720 since 12/28/2017. The exploitability is told to be easy. It is possible to launch the attack remotely. Required for exploitation is a authentication. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 42 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 0.4.7 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: Access controlCWE: CWE-284 / CWE-266
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: assign-deep 0.4.7
Patch: github.com
Timeline
12/28/2017 🔍04/25/2018 🔍
06/06/2018 🔍
06/07/2018 🔍
06/07/2018 🔍
03/21/2023 🔍
Sources
Advisory: 19953a8c089b0328c470acaaaf6accdfcb34da11Status: Not defined
CVE: CVE-2018-3720 (🔍)
GCVE (CVE): GCVE-0-2018-3720
GCVE (VulDB): GCVE-100-119202
Entry
Created: 06/07/2018 10:46Updated: 03/21/2023 21:48
Changes: 06/07/2018 10:46 (60), 02/16/2020 19:39 (1), 03/21/2023 21:48 (5)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.