zephyrproject-rtos 2.2.x MQTT Parser Length Field array index
| 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 rated as critical. This affects an unknown function of the component MQTT Parser. Performing a manipulation as part of Length Field results in array index. This vulnerability is cataloged as CVE-2020-10071. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in zephyrproject-rtos 2.2.x (Project Management Software). It has been classified as critical. This affects an unknown function of the component MQTT Parser. The manipulation as part of a Length Field leads to a array index vulnerability. CWE is classifying the issue as CWE-129. The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The Zephyr MQTT parsing code performs insufficient checking of the length field on publish messages, allowing a buffer overflow and potentially remote code execution. NCC-ZEP-031 This issue affects: zephyrproject-rtos zephyr version 2.2.0 and later versions.
The weakness was shared 06/05/2020. This vulnerability is uniquely identified as CVE-2020-10071 since 03/04/2020. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-156218, VDB-156217, VDB-156216 and VDB-156215 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: Array indexCWE: CWE-129 / CWE-119
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-10071 (🔍)
GCVE (CVE): GCVE-0-2020-10071
GCVE (VulDB): GCVE-100-156219
See also: 🔍
Entry
Created: 06/06/2020 08:57Updated: 10/22/2020 15:50
Changes: 06/06/2020 08:57 (36), 06/06/2020 09:02 (12), 10/22/2020 15:50 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.