Contiki-NG up to 4.1 AQL lvm.c lvm_set_type memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Contiki-NG up to 4.1. This affects the function lvm_set_type of the file os/storage/antelope/lvm.c of the component AQL Handler. Performing a manipulation results in memory corruption.
This vulnerability is reported as CVE-2018-16664. The attack requires a local approach. No exploit exists.
Details
A vulnerability was found in Contiki-NG up to 4.1. It has been classified as critical. This affects the function lvm_set_type of the file os/storage/antelope/lvm.c of the component AQL Handler. The manipulation 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 summary by CVE is:
An issue was discovered in Contiki-NG through 4.1. There is a buffer overflow in lvm_set_type in os/storage/antelope/lvm.c while parsing AQL (lvm_set_op, lvm_set_relation, lvm_set_operand).
The bug was discovered 07/09/2018. The weakness was disclosed 09/07/2018 (Website). It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2018-16664 since 09/07/2018. Attacking locally is a requirement. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 60 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-123750, VDB-123749, VDB-123748 and VDB-123746 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.7
VulDB Base Score: 4.5
VulDB Temp Score: 4.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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
07/09/2018 🔍09/07/2018 🔍
09/07/2018 🔍
09/07/2018 🔍
09/08/2018 🔍
05/07/2023 🔍
Sources
Product: github.comAdvisory: 596
Status: Not defined
CVE: CVE-2018-16664 (🔍)
GCVE (CVE): GCVE-0-2018-16664
GCVE (VulDB): GCVE-100-123747
See also: 🔍
Entry
Created: 09/08/2018 09:06Updated: 05/07/2023 14:44
Changes: 09/08/2018 09:06 (58), 03/21/2020 16:50 (1), 05/07/2023 14:44 (3)
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.