Contiki-NG up to 4.1 MQTT Server parse_publish_vhdr memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.9 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Contiki-NG up to 4.1. This affects the function parse_publish_vhdr of the component MQTT Server. Such manipulation leads to memory corruption.
This vulnerability is listed as CVE-2018-19417. The attack may be performed from remote. There is no available exploit.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in Contiki-NG up to 4.1 and classified as critical. Affected by this issue is the function parse_publish_vhdr of the component MQTT Server. 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. CVE summarizes:
An issue was discovered in the MQTT server in Contiki-NG before 4.2. The function parse_publish_vhdr() that parses MQTT PUBLISH messages with a variable length header uses memcpy to input data into a fixed size buffer. The allocated buffer can fit only MQTT_MAX_TOPIC_LENGTH (default 64) bytes, and a length check is missing. This could lead to Remote Code Execution via a stack-smashing attack (overwriting the function return address). Contiki-NG does not separate the MQTT server from other servers and the OS modules, so access to all memory regions is possible.
The bug was discovered 07/11/2018. The weakness was presented 11/21/2018 (Website). The advisory is available at github.com. This vulnerability is handled as CVE-2018-19417 since 11/21/2018. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 133 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 4.2 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.1VulDB Meta Temp Score: 8.9
VulDB Base Score: 8.3
VulDB Temp Score: 7.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 10.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: 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: Contiki-NG 4.2
Timeline
07/11/2018 🔍11/21/2018 🔍
11/21/2018 🔍
11/21/2018 🔍
11/22/2018 🔍
06/11/2023 🔍
Sources
Product: github.comAdvisory: 600
Status: Not defined
CVE: CVE-2018-19417 (🔍)
GCVE (CVE): GCVE-0-2018-19417
GCVE (VulDB): GCVE-100-127058
Entry
Created: 11/22/2018 08:06Updated: 06/11/2023 09:33
Changes: 11/22/2018 08:06 (58), 04/14/2020 14:13 (1), 06/11/2023 09:33 (4)
Complete: 🔍
Cache ID: 216:486: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.