| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in zephyrproject-rtos 2.2.x. It has been declared as critical. The impacted element is an unknown function of the component MQTT Handler. Such manipulation leads to integer overflow. This vulnerability is listed as CVE-2020-10070. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability was found in zephyrproject-rtos 2.2.x (Project Management Software) and classified as critical. Affected by this issue is some unknown processing of the component MQTT Handler. The manipulation with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In the Zephyr Project MQTT code, improper bounds checking can result in memory corruption and possibly remote code execution. NCC-ZEP-031 This issue affects: zephyrproject-rtos zephyr version 2.2.0 and later versions.
The weakness was presented 06/05/2020. This vulnerability is handled as CVE-2020-10070 since 03/04/2020. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-156219, VDB-156217, VDB-156216 and VDB-156215 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.6VulDB Meta Temp Score: 8.6
VulDB Base Score: 8.3
VulDB Temp Score: 8.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.0
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: 🔍
Exploiting
Class: Integer overflowCWE: CWE-190 / CWE-189
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
03/04/2020 🔍06/05/2020 🔍
06/06/2020 🔍
10/22/2020 🔍
Sources
Status: Not definedCVE: CVE-2020-10070 (🔍)
GCVE (CVE): GCVE-0-2020-10070
GCVE (VulDB): GCVE-100-156218
See also: 🔍
Entry
Created: 06/06/2020 08:57Updated: 10/22/2020 15:44
Changes: 06/06/2020 08:57 (35), 06/06/2020 09:02 (12), 10/22/2020 15:44 (1)
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.