vciy

CVE-2022-3204

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

NRDelegation Attack

CVE-2022-32044 of 4 sources documented this
24

rank 24 = 0 + 19 + 0 + 5 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.01349  ·  without this subject the record ranks 24

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.5, from NVD  ·  without this subject the record ranks 5

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 24

How much of the world it touches

NVD CPE configurations

4 products in the CPE ranges  ·  without this subject the record ranks 19

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 24

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$41,200over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$41,200 = $4.99M incident cost x 0.6121449559255632 exposure x 0.01349 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.01349EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementrisenreceipt
PLATEAU10Minimal movement since 2022-09-27, 1435 days at 0.01, as of 2026-09-01. arc-rules@v1

Foresight · where to check next

CVE-2023-44487SolarWinds Serv-UMicrosoft .NETCVE-2004-1464Cisco IOS XR3204

This record is one instance of CWE-400, uncontrolled resource consumption. The index holds 3763 prior instances of this class, 8 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running NLnet Labs Unbound? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-400 Uncontrolled Resource Consumptionreceipt
Published consequencesCWE-400: Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other)…[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 1 Sep 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD7.5 HIGHreceipt
Exploit probability0.01349 · top 30% of all CVEsreceipt
Blast breadth2 products across 2 vendorsderived
Assigned byNLnet Labsreceipt
Recorded changes34 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productNLnet Labs Unboundreceipt
Published rangesnlnetlabs unbound <= 1.16.2; fedoraproject fedora 35; fedoraproject fedora 36; fedoraproject fedora 37receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

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. receipt

Read the rest of the CNA's description

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.

NVD's analysis a second authority

severity
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
weakness
CWE-400
affected versions
nlnetlabs unbound <= 1.16.2; fedoraproject fedora 35; fedoraproject fedora 36; and 1 more, listed in full below
also scored by
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

check it yourself nlnetlabs.nl lists.fedoraproject.org lists.fedoraproject.org lists.fedoraproject.org security.gentoo.org lists.debian.org receipt

Movement the material steps

27 Sep 20220.00885
7 Mar 20235.7e-4 · scoring model v2023.03.01
17 Mar 20250.00284 · scoring model v2025.03.14
15 Jun 20260.01259 · scoring model v2026.06.15
1 Sep 20260.01349
Show all 34 observations
27 Sep 20220.00885
8 Oct 20220.00954
9 Oct 20220.01018
7 Mar 20235.7e-4
8 Mar 20230.00057
30 Mar 20230.00095
27 Aug 20230.00113
3 Oct 20230.00156
29 Oct 20230.00185
8 Nov 20230.00204
1 Jan 20240.00232
8 Mar 20240.00276
18 Apr 20240.00290
3 May 20240.00336
17 May 20240.00393
17 Dec 20240.00563
17 Mar 20250.00284
29 Mar 20250.00989
30 Mar 20250.00284
20 Jun 20250.00261
12 Jul 20250.00284
23 Jul 20250.00303
27 Sep 20250.00293
14 Oct 20250.0034
18 Nov 20250.01717
21 Nov 20250.0034
16 Jan 20260.00313
27 Jan 20260.00334
14 Feb 20260.00314
5 Mar 20260.00356
15 Jun 20260.01259
7 Jul 20260.01293
27 Jul 20260.01342
1 Sep 20260.01349

34 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.01349Published2022-09-26Index as of2026-09-01

The record had been public for 3 years, 11 months when this index was last written.

Published 2022-09-26 receipt · Index as of 2026-09-01 derived

The pattern, elsewhere

This record is one instance of CWE-400, uncontrolled resource consumption. The index holds 3763 prior instances of this class, 8 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2023-44487matches 8 of 8KEV listed · 2023receipt
CVE-2026-28318 · SolarWinds Serv-Umatches 8 of 9KEV listed · 2026receipt
CVE-2023-38180 · Microsoft .NET 6.0matches 8 of 9KEV listed · 2023receipt
CVE-2004-1464matches 7 of 8KEV listed · 2005receipt
CVE-2020-3566 · Cisco IOS XR Softwarematches 7 of 9KEV listed · 2020receipt
CVE-2020-3569 · Cisco IOS XR Softwarematches 7 of 9KEV listed · 2020receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

3763 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2022-3204.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.