Oppo Smart Phone oppo_vooc.c proc_fastchg_fw_update_write the memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Oppo Smart Phone and classified as critical. Affected by this vulnerability is the function proc_fastchg_fw_update_write of the file /SM8250_Q_Master/android/vendor/oppo_charger/oppo/oppo_vooc.c. The manipulation of the argument the results in memory corruption.
This vulnerability was named CVE-2020-11834. There is no available exploit.
Details
A vulnerability, which was classified as critical, was found in Oppo Smart Phone (Smartphone Operating System) (the affected version is unknown). Affected is the function proc_fastchg_fw_update_write of the file /SM8250_Q_Master/android/vendor/oppo_charger/oppo/oppo_vooc.c. The manipulation of the argument the with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was presented 01/01/2021. The advisory is available at security.oppo.com. This vulnerability is traded as CVE-2020-11834. Technical details are known, but there is no available exploit.
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 best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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/01/2021 🔍01/01/2021 🔍
01/01/2021 🔍
Sources
Advisory: security.oppo.comStatus: Not defined
CVE: CVE-2020-11834 (🔍)
GCVE (CVE): GCVE-0-2020-11834
GCVE (VulDB): GCVE-100-167178
Entry
Created: 01/01/2021 10:24Changes: 01/01/2021 10:24 (38)
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.