PowerDNS Authoritative Server up to 4.0.7/4.1.8 NOTIFY Message resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in PowerDNS Authoritative Server up to 4.0.7/4.1.8. The impacted element is an unknown function of the component NOTIFY Message Handler. Executing a manipulation can lead to resource consumption. This vulnerability is handled as CVE-2019-10163. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability has been found in PowerDNS Authoritative Server up to 4.0.7/4.1.8 (Domain Name Software) and classified as problematic. This vulnerability affects some unknown functionality of the component NOTIFY Message Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. CVE summarizes:
A Vulnerability has been found in PowerDNS Authoritative Server before versions 4.1.9, 4.0.8 allowing a remote, authorized master server to cause a high CPU load or even prevent any further updates to any slave zone by sending a large number of NOTIFY messages. Note that only servers configured as slaves are affected by this issue.
The weakness was released 07/30/2019 (Website). The advisory is shared for download at blog.powerdns.com. This vulnerability was named CVE-2019-10163 since 03/27/2019. The exploitation appears to be easy. The attack can be initiated remotely. A single authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1499.
Upgrading to version 4.0.8 or 4.1.9 eliminates this vulnerability.
Entry connected to this vulnerability is available at VDB-139035. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.0VulDB Meta Temp Score: 4.0
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔍
CNA Base Score: 3.5
CNA Vector (Red Hat, Inc.): 🔍
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: Resource consumptionCWE: 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Authoritative Server 4.0.8/4.1.9
Timeline
03/27/2019 🔍07/30/2019 🔍
07/31/2019 🔍
11/14/2023 🔍
Sources
Advisory: blog.powerdns.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2019-10163 (🔍)
GCVE (CVE): GCVE-0-2019-10163
GCVE (VulDB): GCVE-100-139036
See also: 🔍
Entry
Created: 07/31/2019 09:53Updated: 11/14/2023 11:51
Changes: 07/31/2019 09:53 (58), 07/16/2020 10:46 (1), 11/14/2023 11:51 (14)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.