p PatchFirst

CVE-2020-10995

CVE-2020-10995

This page contains facts from public vulnerability sources. Check the original advisory before updating.

PowerDNS Recursor from 4.1.0 up to and including 4.3.0 does not sufficiently defend against amplification attacks. An issue in the DNS protocol has been found that allow malicious parties to use recursive DNS services to attack third party authoritative name servers. The attack uses a crafted reply by an authoritative name server to amplify the resulting traffic between the recursive and other authoritative name servers. Both types of service can suffer degraded performance as an effect. This is triggered by random subdomains in the NSDNAME in NS records. PowerDNS Recursor 4.1.16, 4.2.2 and 4.3.1 contain a mitigation to limit the impact of this DNS protocol issue.

CVSS 7.5 · High · EPSS 4.5% · Fix available

Published
Updated

Stack: system

Affected products and versions

  • n/a

    Versions
    • n/a: Affected

    No fix published

  • pdns-recursor Debian:12

    Affected ranges
    • ECOSYSTEM: < 4.3.1-1

    Update to 4.3.1-1

  • pdns-recursor Debian:13

    Affected ranges
    • ECOSYSTEM: < 4.3.1-1

    Update to 4.3.1-1

  • pdns-recursor Debian:14

    Affected ranges
    • ECOSYSTEM: < 4.3.1-1

    Update to 4.3.1-1

  • pdns-recursor Ubuntu:Pro:16.04:LTS

    Versions
    • 3.7.3-1
    • 4.0.0~alpha1-1
    • 4.0.0~alpha1-2
    • 4.0.0~alpha2-2
    • 4.0.0~alpha2-2ubuntu0.1
    • 4.0.0~alpha2-2ubuntu0.1+esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • pdns-recursor Ubuntu:Pro:18.04:LTS

    Versions
    • 4.0.6-1
    • 4.0.6-1build1
    • 4.0.7-1
    • 4.1.1-1
    • 4.1.1-1build1
    • 4.1.1-2
    • 4.1.1-2ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • pdns-recursor Ubuntu:Pro:20.04:LTS

    Versions
    • 4.2.0-6
    • 4.2.1-1
    • 4.2.1-1build1
    • 4.2.1-1build2
    • 4.2.1-1ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →