Skip to content
Noroxi
CVE-2022-3204· NVD / CVE Program· CNA NLnet Labs

A vulnerability named 'Non-Responsive Delegation Attack' (NRDelegation Attack) has been discovered in various DNS resolving software.

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 76% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: python3-unbound (AlmaLinux:8) 1.16.2-5.el8; unbound (AlmaLinux:8) 1.16.2-5.el8; unbound-devel (AlmaLinux:8) 1.16.2-5.el8.

Low priority for now. Upgrade to python3-unbound (AlmaLinux:8) 1.16.2-5.el8; unbound (AlmaLinux:8) 1.16.2-5.el8; unbound-devel (AlmaLinux:8) 1.16.2-5.el8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Sep 26, 2022
Updated
Jun 17, 2026
EPSS
1.6% · 76th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.6%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-3204

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
nlnetlabsunbound
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora35
  • fedoraproject fedora36
  • fedoraproject fedora37
  • nlnetlabs unboundup to 1.16.2 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (NLnet Labs). Independent of NVD's CPE analysis and usually ahead of it.

  • NLnet Labs Unbound

    • unspecified and later · up to and including 1.16.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8python3-unboundbefore 1.16.2-5.el81.16.2-5.el8
AlmaLinux:8unboundbefore 1.16.2-5.el81.16.2-5.el8
AlmaLinux:8unbound-develbefore 1.16.2-5.el81.16.2-5.el8
AlmaLinux:8unbound-libsbefore 1.16.2-5.el81.16.2-5.el8
AlmaLinux:9python3-unboundbefore 1.16.2-3.el91.16.2-3.el9
AlmaLinux:9unboundbefore 1.16.2-3.el91.16.2-3.el9
AlmaLinux:9unbound-develbefore 1.16.2-3.el91.16.2-3.el9
AlmaLinux:9unbound-libsbefore 1.16.2-3.el91.16.2-3.el9
Alpine:v3.17unboundbefore 1.16.3-r01.16.3-r0
Debian:10unboundbefore 1.9.0-2+deb10u31.9.0-2+deb10u3
Debian:12unboundbefore 1.16.3-11.16.3-1
openSUSE:Tumbleweedunboundbefore 1.16.3-1.11.16.3-1.1
Red Hat:enterprise_linux:8::appstreampython3-unboundbefore 0:1.16.2-5.el80:1.16.2-5.el8
Red Hat:enterprise_linux:8::appstreampython3-unbound-debuginfobefore 0:1.16.2-5.el80:1.16.2-5.el8
Red Hat:enterprise_linux:8::appstreamunboundbefore 0:1.16.2-5.el80:1.16.2-5.el8
Red Hat:enterprise_linux:8::appstreamunbound-debuginfobefore 0:1.16.2-5.el80:1.16.2-5.el8
Red Hat:enterprise_linux:8::appstreamunbound-debugsourcebefore 0:1.16.2-5.el80:1.16.2-5.el8
Red Hat:enterprise_linux:8::appstreamunbound-develbefore 0:1.16.2-5.el80:1.16.2-5.el8
Red Hat:enterprise_linux:8::appstreamunbound-libsbefore 0:1.16.2-5.el80:1.16.2-5.el8
Red Hat:enterprise_linux:8::appstreamunbound-libs-debuginfobefore 0:1.16.2-5.el80:1.16.2-5.el8
Red Hat:enterprise_linux:9::appstreampython3-unboundbefore 0:1.16.2-3.el90:1.16.2-3.el9
Red Hat:enterprise_linux:9::appstreampython3-unbound-debuginfobefore 0:1.16.2-3.el90:1.16.2-3.el9
Red Hat:enterprise_linux:9::appstreamunboundbefore 0:1.16.2-3.el90:1.16.2-3.el9
Red Hat:enterprise_linux:9::appstreamunbound-debuginfobefore 0:1.16.2-3.el90:1.16.2-3.el9

+17

Other highest-scoring records for the same primary product.

  • CVE-2019-25042Unbound before 1.9.5 allows an out-of-bounds write via a compressed name in rdata_copy.
    40Plan
  • CVE-2019-25039Unbound before 1.9.5 allows an integer overflow in a size calculation in respip/respip.c.
    40Plan
  • CVE-2019-25038Unbound before 1.9.5 allows an integer overflow in a size calculation in dnscrypt/dnscrypt.c.
    40Plan
  • CVE-2019-25035Unbound before 1.9.5 allows an out-of-bounds write in sldns_bget_token_par.
    40Plan
  • CVE-2019-25034Unbound before 1.9.5 allows an integer overflow in sldns_str2wire_dname_buf_origin, leading to an out-of-bounds write.
    40Plan
  • CVE-2019-25033Unbound before 1.9.5 allows an integer overflow in the regional allocator via the ALIGN_UP macro.
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:python3-unbound1.16.2-3.el9 · AlmaLinux:9Package registry (OSV)
almalinux:unbound1.16.2-3.el9 · AlmaLinux:9Package registry (OSV)
almalinux:unbound-devel1.16.2-3.el9 · AlmaLinux:9Package registry (OSV)
almalinux:unbound-libs1.16.2-3.el9 · AlmaLinux:9Package registry (OSV)
alpine:unbound1.16.3-r0 · Alpine:v3.17Package registry (OSV)
debian:unbound1.16.3-1 · Debian:12Package registry (OSV)
opensuse:unbound1.20.0-150600.23.3.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:python3-unbound0:1.16.2-3.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:python3-unbound-debuginfo0:1.16.2-3.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:unbound0:1.16.2-3.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:unbound-debuginfo0:1.16.2-3.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:unbound-debugsource0:1.16.2-3.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:unbound-devel0:1.16.2-3.el9 · Red Hat:enterprise_linux:9::crbPackage registry (OSV)
red hat:unbound-libs0:1.16.2-3.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:unbound-libs-debuginfo0:1.16.2-3.el9 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:unbound0:1.16.2-5.12.el8_10 · Rocky Linux:8Package registry (OSV)
suse:unbound1.20.0-150600.23.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

  • Yehuda AfekTel-Aviv University, Anat Bremler-Barr and Shani Stajnrod

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
function expand(node) {  return node.children.map(expand);}

Fixed

ts
const MAX_DEPTH = 32;function expand(node, depth = 0) {  if (depth > MAX_DEPTH) throw new Error("too deep");  return node.children.map((c) => expand(c, depth + 1));}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records