FNET up to 4.6.4/6.c IPv6 Fragmentation fnet_ip6.c _fnet_ip6_reassembly uninitialized pointer
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in FNET up to 4.6.4/6.c. This issue affects the function _fnet_ip6_reassembly of the file fnet_ip6.c of the component IPv6 Fragmentation Handler. This manipulation causes uninitialized pointer.
This vulnerability appears as CVE-2020-17469. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in FNET up to 4.6.4/6.c. It has been declared as problematic. Affected by this vulnerability is the function _fnet_ip6_reassembly of the file fnet_ip6.c of the component IPv6 Fragmentation Handler. The manipulation with an unknown input leads to a uninitialized pointer vulnerability. The CWE definition for the vulnerability is CWE-824. The product accesses or uses a pointer that has not been initialized. As an impact it is known to affect availability.
The weakness was presented 12/12/2020 as icsa-20-343-01. The advisory is shared at us-cert.cisa.gov. This vulnerability is known as CVE-2020-17469. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Uninitialized pointerCWE: CWE-824 / CWE-908
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/10/2020 🔍12/12/2020 🔍
12/12/2020 🔍
12/16/2020 🔍
Sources
Advisory: icsa-20-343-01Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-17469 (🔍)
GCVE (CVE): GCVE-0-2020-17469
GCVE (VulDB): GCVE-100-166093
Entry
Created: 12/12/2020 07:15Updated: 12/16/2020 14:10
Changes: 12/12/2020 07:15 (37), 12/16/2020 14:10 (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.