Contiki-NG up to 4.1 AQL aql-lexer.c next_string memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Contiki-NG up to 4.1 and classified as critical. Affected is the function next_string of the file os/storage/antelope/aql-lexer.c of the component AQL Handler. The manipulation leads to memory corruption.
This vulnerability is traded as CVE-2018-16666. An attack has to be approached locally. There is no exploit available.
Details
A vulnerability was found in Contiki-NG up to 4.1. It has been rated as critical. This issue affects the function next_string of the file os/storage/antelope/aql-lexer.c of the component AQL Handler. 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:
An issue was discovered in Contiki-NG through 4.1. There is a stack-based buffer overflow in next_string in os/storage/antelope/aql-lexer.c while parsing AQL (parsing next string).
The bug was discovered 07/09/2018. The weakness was shared 09/07/2018 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2018-16666 since 09/07/2018. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
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-123748, VDB-123747 and VDB-123746 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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: 595
Status: Not defined
CVE: CVE-2018-16666 (🔍)
GCVE (CVE): GCVE-0-2018-16666
GCVE (VulDB): GCVE-100-123749
See also: 🔍
Entry
Created: 09/08/2018 09:07Updated: 05/07/2023 14:51
Changes: 09/08/2018 09:07 (58), 03/21/2020 17:05 (1), 05/07/2023 14:51 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.