CVE-2015-1868

UnknownEPSS 81.83%

Last modified

CVE-2015-1868 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 81.83% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
81.83%

99.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
PowerdnsAuthoritative3.2
PowerdnsAuthoritative3.3
PowerdnsAuthoritative3.3.1
PowerdnsAuthoritative3.3.2
PowerdnsAuthoritative3.4.0
PowerdnsAuthoritative3.4.1
PowerdnsAuthoritative3.4.3
FedoraprojectFedora20
FedoraprojectFedora21
FedoraprojectFedora22
PowerdnsRecursor3.5
PowerdnsRecursor3.5.1
PowerdnsRecursor3.5.2
PowerdnsRecursor3.5.3
PowerdnsRecursor3.6.0
PowerdnsRecursor3.6.1
PowerdnsRecursor3.6.2
PowerdnsRecursor3.6.3
PowerdnsRecursor3.7.1

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2015-1868?
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.
How severe is CVE-2015-1868?
Severity scoring for CVE-2015-1868 is pending analysis. The EPSS model estimates a 81.83% probability of exploitation in the next 30 days.
How do I fix CVE-2015-1868?
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-2015-1868?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST