zephyrproject-rtos zephyr 2.1.x JSON Parser updatehub_probe memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in zephyrproject-rtos zephyr 2.1.x. It has been classified as critical. The affected element is the function updatehub_probe of the component JSON Parser. The manipulation leads to memory corruption.
This vulnerability is referenced as CVE-2020-10060. Remote exploitation of the attack is possible. No exploit is available.
Upgrading the affected component is recommended.
Details
A vulnerability was found in zephyrproject-rtos zephyr 2.1.x (Project Management Software) and classified as critical. This issue affects the function updatehub_probe of the component JSON Parser. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In updatehub_probe, right after JSON parsing is complete, objects\[1] is accessed from the output structure in two different places. If the JSON contained less than two elements, this access would reference unitialized stack memory. This could result in a crash, denial of service, or possibly an information leak. Recommend disabling updatehub until such a time as a fix can be made available. Provided the fix in CVE-2020-10059 is applied, the attack requires compromise of the server. See NCC-ZEP-030 This issue affects: zephyrproject-rtos zephyr version 2.1.0 and later versions. version 2.2.0 and later versions.
The weakness was published 05/11/2020. The identification of this vulnerability is CVE-2020-10060 since 03/04/2020. The attack may be initiated remotely. The exploitation requires an enhanced level of successful authentication. Technical details are known, but no exploit is available.
Upgrading to version 2.2.0 eliminates this vulnerability.
Similar entries are available at VDB-154986, VDB-154984, VDB-154983 and VDB-154982. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 6.6
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: Memory corruptionCWE: 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: zephyr 2.2.0
Timeline
03/04/2020 🔍05/11/2020 🔍
05/12/2020 🔍
10/16/2020 🔍
Sources
Product: github.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-10060 (🔍)
GCVE (CVE): GCVE-0-2020-10060
GCVE (VulDB): GCVE-100-154985
See also: 🔍
Entry
Created: 05/12/2020 07:42Updated: 10/16/2020 13:54
Changes: 05/12/2020 07:42 (40), 05/12/2020 07:47 (12), 10/16/2020 13:50 (1), 10/16/2020 13:54 (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.