OpenTrace 1.0 Cloud Functions Subsystem Request dynamically-determined object attributes
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in OpenTrace 1.0. This vulnerability affects unknown code of the component Cloud Functions Subsystem. This manipulation as part of Request causes dynamically-determined object attributes. The identification of this vulnerability is CVE-2020-11872. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in OpenTrace 1.0. It has been declared as critical. Affected by this vulnerability is some unknown processing of the component Cloud Functions Subsystem. The manipulation as part of a Request leads to a dynamically-determined object attributes vulnerability. The CWE definition for the vulnerability is CWE-915. The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified. As an impact it is known to affect integrity. The summary by CVE is:
The Cloud Functions subsystem in OpenTrace 1.0 might allow fabrication attacks by making billions of TempID requests before an AES-256-GCM key rotation occurs.
The weakness was shared 04/17/2020. This vulnerability is known as CVE-2020-11872 since 04/17/2020. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. Harrison Grundy, one of the authors explains: "Unfortunately, the way the current implementation works, it does not require active exploitation by a malicious actor, the server will continue to send TempIDs beyond the useful life of the encryption key. Based on the default settings of the application, this occurs after ~1B "user/hours" or about 1.5M users over a 30 day period."
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.7
VulDB Base Score: 5.9
VulDB Temp Score: 5.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Dynamically-determined object attributesCWE: CWE-915 / CWE-913
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
04/17/2020 🔍04/17/2020 🔍
04/18/2020 🔍
05/31/2024 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2020-11872 (🔍)
GCVE (CVE): GCVE-0-2020-11872
GCVE (VulDB): GCVE-100-154069
Entry
Created: 04/18/2020 09:07Updated: 05/31/2024 15:29
Changes: 04/18/2020 09:07 (35), 07/28/2020 07:16 (17), 05/31/2024 15:29 (17)
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.