RIOT IPv6 Address ipv6_addr_from_str.c ipv6_addr_from_str memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.1 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in RIOT. This impacts the function ipv6_addr_from_str of the file sys/net/network_layer/ipv6/addr/ipv6_addr_from_str.c of the component IPv6 Address Handler. The manipulation results in memory corruption.
This vulnerability is identified as CVE-2017-8289. The attack can be executed remotely. There is not any exploit available.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in RIOT (affected version unknown). It has been classified as critical. Affected is the function ipv6_addr_from_str of the file sys/net/network_layer/ipv6/addr/ipv6_addr_from_str.c of the component IPv6 Address 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. CVE summarizes:
Stack-based buffer overflow in the ipv6_addr_from_str function in sys/net/network_layer/ipv6/addr/ipv6_addr_from_str.c in RIOT prior to 2017-04-25 allows local attackers, and potentially remote attackers, to cause a denial of service or possibly have unspecified other impact via a malformed IPv6 address.
The bug was discovered 04/26/2017. The weakness was released 04/27/2017 (GitHub Repository). The advisory is available at github.com. This vulnerability is traded as CVE-2017-8289 since 04/26/2017. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.
Upgrading eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.1
VulDB Base Score: 7.3
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.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: 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: 🔍
Patch: github.com
Timeline
04/25/2017 🔍04/26/2017 🔍
04/26/2017 🔍
04/26/2017 🔍
04/27/2017 🔍
04/27/2017 🔍
12/02/2022 🔍
Sources
Advisory: 6840Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-8289 (🔍)
GCVE (CVE): GCVE-0-2017-8289
GCVE (VulDB): GCVE-100-100626
OSVDB: - CVE-2017-8289 - Riot Project - Riot - High
Entry
Created: 04/27/2017 16:50Updated: 12/02/2022 11:14
Changes: 04/27/2017 16:50 (57), 09/21/2020 16:17 (3), 12/02/2022 11:14 (5)
Complete: 🔍
Cache ID: 216:0E0: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.