TypeORM up to 0.2.24 Object Prototype modification of assumed-immutable data
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in TypeORM up to 0.2.24. This affects an unknown part. Performing a manipulation as part of Object results in modification of assumed-immutable data (Prototype). This vulnerability is known as CVE-2020-8158. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability, which was classified as critical, was found in TypeORM up to 0.2.24. This affects some unknown functionality. The manipulation as part of a Object leads to a modification of assumed-immutable data vulnerability (Prototype). CWE is classifying the issue as CWE-471. The product does not properly protect an assumed-immutable element from being modified by an attacker. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Prototype pollution vulnerability in the TypeORM package < 0.2.25 may allow attackers to add or modify Object properties leading to further denial of service or SQL injection attacks.
The weakness was published 09/18/2020 (Website). The advisory is shared at hackerone.com. This vulnerability is uniquely identified as CVE-2020-8158 since 01/28/2020. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
- 0.2.0
- 0.2.1
- 0.2.2
- 0.2.3
- 0.2.4
- 0.2.5
- 0.2.6
- 0.2.7
- 0.2.8
- 0.2.9
- 0.2.10
- 0.2.11
- 0.2.12
- 0.2.13
- 0.2.14
- 0.2.15
- 0.2.16
- 0.2.17
- 0.2.18
- 0.2.19
- 0.2.20
- 0.2.21
- 0.2.22
- 0.2.23
- 0.2.24
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: Modification of assumed-immutable data / Prototype
CWE: CWE-471
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/28/2020 🔍09/18/2020 🔍
09/19/2020 🔍
09/19/2020 🔍
Sources
Advisory: hackerone.comStatus: Not defined
CVE: CVE-2020-8158 (🔍)
GCVE (CVE): GCVE-0-2020-8158
GCVE (VulDB): GCVE-100-161625
Entry
Created: 09/19/2020 14:37Updated: 09/19/2020 14:42
Changes: 09/19/2020 14:37 (37), 09/19/2020 14:42 (17)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.