Kea DHCP up to 1.5.0/1.6.0-beta2 Request input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Kea DHCP up to 1.5.0/1.6.0-beta2. Affected by this issue is some unknown functionality. Executing a manipulation as part of Request can lead to input validation. This vulnerability appears as CVE-2019-6474. The attacker needs to be present on the local network. There is no available exploit.
Details
A vulnerability classified as problematic was found in Kea DHCP up to 1.5.0/1.6.0-beta2. This vulnerability affects an unknown code block. The manipulation as part of a Request leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect availability. CVE summarizes:
A missing check on incoming client requests can be exploited to cause a situation where the Kea server's lease storage contains leases which are rejected as invalid when the server tries to load leases from storage on restart. If the number of such leases exceeds a hard-coded limit in the Kea code, a server trying to restart will conclude that there is a problem with its lease store and give up. Versions affected: 1.4.0 to 1.5.0, 1.6.0-beta1, and 1.6.0-beta2
The weakness was presented 10/16/2019 (Website). The advisory is shared for download at kb.isc.org. This vulnerability was named CVE-2019-6474 since 01/16/2019. Access to the local network is required for this attack. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.9
VulDB Base Score: 5.7
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Kea): 5.7
Vendor Vector (Kea): 🔍
Researcher Base Score: 5.7
Researcher Vector: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 5.7
CNA Vector (Internet Systems Consortium (ISC)): 🔍
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: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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/16/2019 🔍10/16/2019 🔍
10/18/2019 🔍
01/16/2024 🔍
Sources
Advisory: kb.isc.orgStatus: Not defined
CVE: CVE-2019-6474 (🔍)
GCVE (CVE): GCVE-0-2019-6474
GCVE (VulDB): GCVE-100-143848
Entry
Created: 10/18/2019 10:06Updated: 01/16/2024 11:22
Changes: 10/18/2019 10:06 (55), 10/18/2019 10:11 (17), 01/16/2024 11:22 (12)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.