openSUSE wicked up to 0.6.55 ni_dhcp4_parse_response release of resource
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in openSUSE wicked up to 0.6.55. This issue affects the function ni_dhcp4_parse_response. This manipulation causes release of resource.
This vulnerability is registered as CVE-2020-7216. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as problematic was found in openSUSE wicked up to 0.6.55. Affected by this vulnerability is the function ni_dhcp4_parse_response. The manipulation with an unknown input leads to a release of resource vulnerability. The CWE definition for the vulnerability is CWE-772. The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed. As an impact it is known to affect availability. The summary by CVE is:
An ni_dhcp4_parse_response memory leak in openSUSE wicked 0.6.55 and earlier allows network attackers to cause a denial of service by sending DHCP4 packets without a message type option.
The weakness was published 02/05/2020 (Website). The advisory is shared at lists.opensuse.org. This vulnerability is known as CVE-2020-7216 since 01/17/2020. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
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
Vendor
Name
Version
- 0.6.0
- 0.6.1
- 0.6.2
- 0.6.3
- 0.6.4
- 0.6.5
- 0.6.6
- 0.6.7
- 0.6.8
- 0.6.9
- 0.6.10
- 0.6.11
- 0.6.12
- 0.6.13
- 0.6.14
- 0.6.15
- 0.6.16
- 0.6.17
- 0.6.18
- 0.6.19
- 0.6.20
- 0.6.21
- 0.6.22
- 0.6.23
- 0.6.24
- 0.6.25
- 0.6.26
- 0.6.27
- 0.6.28
- 0.6.29
- 0.6.30
- 0.6.31
- 0.6.32
- 0.6.33
- 0.6.34
- 0.6.35
- 0.6.36
- 0.6.37
- 0.6.38
- 0.6.39
- 0.6.40
- 0.6.41
- 0.6.42
- 0.6.43
- 0.6.44
- 0.6.45
- 0.6.46
- 0.6.47
- 0.6.48
- 0.6.49
- 0.6.50
- 0.6.51
- 0.6.52
- 0.6.53
- 0.6.54
- 0.6.55
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Release of resourceCWE: CWE-772 / CWE-400 / CWE-404
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
01/17/2020 🔍02/05/2020 🔍
02/06/2020 🔍
02/06/2020 🔍
Sources
Advisory: lists.opensuse.orgStatus: Not defined
CVE: CVE-2020-7216 (🔍)
GCVE (CVE): GCVE-0-2020-7216
GCVE (VulDB): GCVE-100-149725
Entry
Created: 02/06/2020 11:21Updated: 02/06/2020 11:26
Changes: 02/06/2020 11:21 (37), 02/06/2020 11:26 (17)
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.