The label decompression functionality in PowerDNS Recursor 3.5.x, 3.6.x before 3.6.3, and 3.7.x before 3.7.2 and…
No fixed version listed yet.Check the vendor advisory. References ↓
The label decompression functionality in PowerDNS Recursor (3.5.x, 3.6.x before 3.6.3, and 3.7.x before 3.7.2) and PowerDNS Authoritative (Auth) Server (3.2.x, 3.3.x before 3.3.2, and 3.4.x before 3.4.4) mishandles DNS names. A remote attacker can send a crafted request containing a name that refers to itself to cause a denial of service through CPU exhaustion or a crash.
Official description · CVE.org
The label decompression functionality in PowerDNS Recursor 3.5.x, 3.6.x before 3.6.3, and 3.7.x before 3.7.2 and Authoritative (Auth) Server 3.2.x, 3.3.x before 3.3.2, and 3.4.x before 3.4.4 allows remote attackers to cause a denial of service (CPU consumption or crash) via a request with a name that refers to itself.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 18 May 2015. No public exploit code or confirmed exploitation is recorded.
Patch historyEarlier and later CVEs in the same code, in date order. It shows when a fix was bypassed or incomplete and which version finally fixed it.
A fix was bypassed or incomplete once over 6 months.
Linked vulnerabilitiesLinked by evidence that a fix failed or the same code was patched again. Oldest first.
- This CVECVE-2015-1868The label decompression functionality in PowerDNS Recursor…18 May 2015
incomplete fixHigh
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Stated in the CVE text
NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-1868.
- Stated in the CVE text