CVE-2025-59030
BaseFortify
Publication date: 2025-12-09
Last updated on: 2026-02-19
Assigner: Open-Xchange
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| powerdns | recursor | From 5.1.0 (inc) to 5.1.9 (exc) |
| powerdns | recursor | From 5.2.0 (inc) to 5.2.7 (exc) |
| powerdns | recursor | From 5.3.0 (inc) to 5.3.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-276 | During installation, installed file permissions are set to allow anyone to modify those files. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability allows an attacker to remove cached records by sending a NOTIFY query over TCP, which can disrupt normal operations by forcing the system to lose cached data.
How can this vulnerability impact me? :
The impact of this vulnerability is a denial of service condition where cached records are removed unexpectedly, potentially causing service disruption or degraded performance.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability impacts availability by enabling a denial of service through cache clearing but does not affect confidentiality or integrity of data. Therefore, it does not directly impact compliance with standards focused on data protection such as GDPR or HIPAA, which emphasize confidentiality and integrity. However, organizations should consider availability requirements in their compliance frameworks and mitigate the vulnerability accordingly. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can involve monitoring for unexpected or suspicious DNS NOTIFY messages over TCP, which are unusual since NOTIFY is typically sent over UDP. Network traffic capture tools like tcpdump or Wireshark can be used to filter and inspect DNS NOTIFY messages over TCP. For example, using tcpdump: tcpdump -i <interface> 'tcp port 53 and (udp[10] = 4)' (Note: Adjust the filter to capture DNS NOTIFY over TCP). Additionally, checking logs of the PowerDNS Recursor for unexpected cache clear events or unusual NOTIFY queries may help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include upgrading PowerDNS Recursor to patched versions 5.3.3, 5.2.7, or 5.1.9. If upgrading is not immediately possible, blocking incoming DNS NOTIFY messages over TCP at the network firewall or server level is recommended to prevent exploitation. [1]