Vivo ABE Versions earlier than 4.4.0.9 Command input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Vivo ABE Versions earlier than 4.4.0.9. Affected is an unknown function of the component Command Handler. Performing a manipulation results in input validation. This vulnerability is known as CVE-2020-12487. The attack may be carried out on the physical device. No exploit is available.
Details
A vulnerability, which was classified as critical, was found in Vivo ABE Versions earlier than 4.4.0.9. This affects an unknown code of the component Command Handler. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Due to the flaws in the verification of input parameters, the attacker can input carefully constructed commands to make the ABE service execute some commands with root privilege.
The advisory is shared at vivo.com. This vulnerability is uniquely identified as CVE-2020-12487 since 04/30/2020. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. 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
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.8
VulDB Base Score: 6.6
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.0
CNA Vector (Vivo): 🔍
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: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
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
04/30/2020 🔍12/17/2024 🔍
12/17/2024 🔍
02/17/2025 🔍
Sources
Advisory: vivo.comStatus: Confirmed
CVE: CVE-2020-12487 (🔍)
GCVE (CVE): GCVE-0-2020-12487
GCVE (VulDB): GCVE-100-288705
Entry
Created: 12/17/2024 07:59Updated: 02/17/2025 05:22
Changes: 12/17/2024 07:59 (61), 02/17/2025 05:22 (1)
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.