CVE-2006-4252
UnknownEPSS 5.91%
Last modified
CVE-2006-4252 is a vulnerability of currently unknown severity. PowerDNS Recursor 3.1.3 and earlier allows remote attackers to cause a denial of service (resource exhaustion and application crash) via a CNAME record with a zero TTL, which triggers an infinite loop.. EPSS estimates a 5.91% chance of exploitation in the next 30 days.
Description
PowerDNS Recursor 3.1.3 and earlier allows remote attackers to cause a denial of service (resource exhaustion and application crash) via a CNAME record with a zero TTL, which triggers an infinite loop.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Powerdns | Recursor | <= 3.1.3 |
| Powerdns | Recursor | 2.0_rc1 |
| Powerdns | Recursor | 2.8 |
| Powerdns | Recursor | 2.9.15 |
| Powerdns | Recursor | 2.9.16 |
| Powerdns | Recursor | 2.9.17 |
| Powerdns | Recursor | 2.9.18 |
| Powerdns | Recursor | 3.0 |
| Powerdns | Recursor | 3.0.1 |
| Powerdns | Recursor | 3.1 |
| Powerdns | Recursor | 3.1.1 |
| Powerdns | Recursor | 3.1.2 |
References
- http://doc.powerdns.com/powerdns-advisory-2006-02.htmlPatch, Vendor Advisory
- http://secunia.com/advisories/22824Patch, Vendor Advisory
- http://doc.powerdns.com/powerdns-advisory-2006-02.htmlPatch, Vendor Advisory
- http://secunia.com/advisories/22824Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2006-4252?
PowerDNS Recursor 3.1.3 and earlier allows remote attackers to cause a denial of service (resource exhaustion and application crash) via a CNAME record with a zero TTL, which triggers an infinite loop.
How severe is CVE-2006-4252?
Severity scoring for CVE-2006-4252 is pending analysis. The EPSS model estimates a 5.91% probability of exploitation in the next 30 days.
How do I fix CVE-2006-4252?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2006-4252?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
