CVE-2015-1868: High severity PowerDNS Authoritative vulnerability

Published May 18, 2015
·
Updated

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.

Affected Software

19 affected components
PowerDNS Authoritative=3.2
PowerDNS Authoritative=3.3
PowerDNS Authoritative=3.3.1
PowerDNS Authoritative=3.3.2
PowerDNS Authoritative=3.4.0
PowerDNS Authoritative=3.4.1
PowerDNS Authoritative=3.4.3
Fedoraproject Fedora=20
Fedoraproject Fedora=21
Fedoraproject Fedora=22
PowerDNS recursor=3.5
PowerDNS recursor=3.5.1
PowerDNS recursor=3.5.2
PowerDNS recursor=3.5.3
PowerDNS recursor=3.6.0
PowerDNS recursor=3.6.1
PowerDNS recursor=3.6.2
PowerDNS recursor=3.6.3
PowerDNS recursor=3.7.1

Event History

May 18, 2015
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2015-1868?

CVE-2015-1868 is classified as a denial of service vulnerability due to high CPU consumption or crashes.

2

How do I fix CVE-2015-1868?

To fix CVE-2015-1868, upgrade PowerDNS Recursor to version 3.6.3 or later, and Authoritative Server to version 3.3.2 or later.

3

Which versions of PowerDNS are affected by CVE-2015-1868?

CVE-2015-1868 affects PowerDNS Recursor versions 3.5.x, 3.6.x prior to 3.6.3, and 3.7.x prior to 3.7.2; and Authoritative Server versions 3.2.x, 3.3.x prior to 3.3.2, and 3.4.x prior to 3.4.4.

4

What could an attacker achieve by exploiting CVE-2015-1868?

An attacker exploiting CVE-2015-1868 can cause a denial of service condition, impacting service availability.

5

Are there any workarounds for CVE-2015-1868?

There are no specific workarounds for CVE-2015-1868; users are advised to upgrade to the fixed versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203