lodash up to 4.17.15 _.zipObjectDeep Prototype allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in lodash up to 4.17.15. It has been rated as critical. The affected element is the function _.zipObjectDeep. Performing a manipulation results in allocation of resources (Prototype).
This vulnerability is identified as CVE-2020-8203. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as critical has been found in lodash up to 4.17.15. This affects the function _.zipObjectDeep. The manipulation with an unknown input leads to a allocation of resources vulnerability (Prototype). CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Prototype pollution attack when using _.zipObjectDeep in lodash <= 4.17.15.
The weakness was released 07/15/2020 (Website). It is possible to read the advisory at hackerone.com. This vulnerability is uniquely identified as CVE-2020-8203 since 01/28/2020. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
The vulnerability scanner Nessus provides a plugin with the ID 297644 (Atlassian Jira Service Management Data Center and Server 10.3.x < 10.3.12 / 11.0.x < 11.1.0 (JSDSERVER-16479)), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Tenable (297644). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 4.17.0
- 4.17.1
- 4.17.2
- 4.17.3
- 4.17.4
- 4.17.5
- 4.17.6
- 4.17.7
- 4.17.8
- 4.17.9
- 4.17.10
- 4.17.11
- 4.17.12
- 4.17.13
- 4.17.14
- 4.17.15
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
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
Name: PrototypeClass: Allocation of resources / Prototype
CWE: CWE-770 / CWE-400 / CWE-404
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 |
Nessus ID: 297644
Nessus Name: Atlassian Jira Service Management Data Center and Server 10.3.x < 10.3.12 / 11.0.x < 11.1.0 (JSDSERVER-16479)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/28/2020 🔍07/15/2020 🔍
07/16/2020 🔍
02/03/2026 🔍
Sources
Advisory: hackerone.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-8203 (🔍)
GCVE (CVE): GCVE-0-2020-8203
GCVE (VulDB): GCVE-100-158571
Entry
Created: 07/16/2020 12:08Updated: 02/03/2026 18:17
Changes: 07/16/2020 12:08 (37), 07/16/2020 12:13 (17), 11/03/2020 07:54 (1), 02/03/2026 18:17 (18)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.