p PatchFirst

CVE-2022-3204

CVE-2022-3204 · NRDelegation Attack

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

A vulnerability named 'Non-Responsive Delegation Attack' (NRDelegation Attack) has been discovered in various DNS resolving software. The NRDelegation Attack works by having a malicious delegation with a considerable number of non responsive nameservers. The attack starts by querying a resolver for a record that relies on those unresponsive nameservers. The attack can cause a resolver to spend a lot of time/resources resolving records under a malicious delegation point where a considerable number of unresponsive NS records reside. It can trigger high CPU usage in some resolver implementations that continually look in the cache for resolved NS records in that delegation. This can lead to degraded performance and eventually denial of service in orchestrated attacks. Unbound does not suffer from high CPU usage, but resources are still needed for resolving the malicious delegation. Unbound will keep trying to resolve the record until hard limits are reached. Based on the nature of the attack and the replies, different limits could be reached. From version 1.16.3 on, Unbound introduces fixes for better performance when under load, by cutting opportunistic queries for nameserver discovery and DNSKEY prefetching and limiting the number of times a delegation point can issue a cache lookup for missing records.

CVSS 7.5 · High · EPSS 1.6% · Fix available

Published
Updated

Stack: system

Affected products and versions

  • unbound

    Versions
    • ≥ unspecified, ≤ 1.16.2: Affected (custom)

    No fix published

  • unbound Debian:12

    Affected ranges
    • ECOSYSTEM: < 1.16.3-1

    Update to 1.16.3-1

  • unbound Debian:13

    Affected ranges
    • ECOSYSTEM: < 1.16.3-1

    Update to 1.16.3-1

  • unbound Debian:14

    Affected ranges
    • ECOSYSTEM: < 1.16.3-1

    Update to 1.16.3-1

  • unbound Ubuntu:Pro:14.04:LTS

    Versions
    • 1.4.20-1
    • 1.4.21-1
    • 1.4.21-1ubuntu1
    • 1.4.21-1ubuntu2
    • 1.4.22-1ubuntu1
    • 1.4.22-1ubuntu2
    • 1.4.22-1ubuntu3
    • 1.4.22-1ubuntu4
    • 1.4.22-1ubuntu4.14.04.1
    • 1.4.22-1ubuntu4.14.04.2
    • 1.4.22-1ubuntu4.14.04.3
    • 1.4.22-1ubuntu4.14.04.3+esm1
    • 1.4.22-1ubuntu4.14.04.3+esm2
    • 1.4.22-1ubuntu4.14.04.3+esm3
    • 1.4.22-1ubuntu4.14.04.3+esm4
    • 1.4.22-1ubuntu4.14.04.3+esm5
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • unbound Ubuntu:Pro:16.04:LTS

    Versions
    • 1.4.22-1ubuntu6
    • 1.5.7-1ubuntu1
    • 1.5.7-1ubuntu2
    • 1.5.8-1ubuntu1
    • 1.5.8-1ubuntu1.1
    • 1.5.8-1ubuntu1.1+esm1
    • 1.5.8-1ubuntu1.1+esm2
    • 1.5.8-1ubuntu1.1+esm3
    • 1.5.8-1ubuntu1.1+esm4
    • 1.5.8-1ubuntu1.1+esm5
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • unbound Ubuntu:18.04:LTS

    Versions
    • 1.6.5-1
    • 1.6.7-1
    • 1.6.7-1build1
    • 1.6.7-1ubuntu1
    • 1.6.7-1ubuntu2
    • 1.6.7-1ubuntu2.1
    • 1.6.7-1ubuntu2.2
    • 1.6.7-1ubuntu2.3
    • 1.6.7-1ubuntu2.4
    • 1.6.7-1ubuntu2.5
    Affected ranges
    • ECOSYSTEM: < 1.6.7-1ubuntu2.6

    Update to 1.6.7-1ubuntu2.6

  • unbound Ubuntu:20.04:LTS

    Versions
    • 1.9.0-2ubuntu1
    • 1.9.0-2ubuntu2
    • 1.9.4-2
    • 1.9.4-2ubuntu1
    • 1.9.4-2ubuntu1.1
    • 1.9.4-2ubuntu1.2
    • 1.9.4-2ubuntu1.3
    Affected ranges
    • ECOSYSTEM: < 1.9.4-2ubuntu1.4

    Update to 1.9.4-2ubuntu1.4

  • unbound Ubuntu:22.04:LTS

    Versions
    • 1.13.1-1ubuntu1
    • 1.13.1-1ubuntu3
    • 1.13.1-1ubuntu5
    • 1.13.1-1ubuntu5.1
    • 1.13.1-1ubuntu5.2
    Affected ranges
    • ECOSYSTEM: < 1.13.1-1ubuntu5.3

    Update to 1.13.1-1ubuntu5.3

Original sources

Check your server →