CVE-2022-3094 [High] | Denial of Service in Bind

Sending a flood of dynamic DNS updates may cause `named` to allocate large amounts of memory. This, in turn, may cause `named` to exit due to a lack of free memory. We are not aware of any cases where this has been exploited. Memory is allocated prior to the checking of access permissions (ACLs) and is retained during the processing of a dynamic update from a client whose access credentials are accepted. Memory allocated to clients that are not permitted to send updates is released immediately upon rejection. The scope of this vulnerability is limited therefore to trusted clients who are permitted to make dynamic zone changes. If a dynamic update is REFUSED, memory will be released again very quickly. Therefore it is only likely to be possible to degrade or stop `named` by sending a flood of unaccepted dynamic updates comparable in magnitude to a query flood intended to achieve the same detrimental outcome. BIND 9.11 and earlier branches are also affected, but through exhaustion of internal resources rather than memory constraints. This may reduce performance but should not be a significant problem for most servers. Therefore we don't intend to address this for BIND versions prior to BIND 9.16. This issue affects BIND 9 versions 9.16.0 through 9.16.36, 9.18.0 through 9.18.10, 9.19.0 through 9.19.8, and 9.16.8-S1 through 9.16.36-S1.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-18	13.21%	13.11%	-0.10%
2	2026-06-15	2.34%	13.21%	+10.88%
3	2026-05-17	—	2.34%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-18

13.21%

13.11%

-0.10%

2026-06-15

2.34%

13.21%

+10.88%

2026-05-17

—

2.34%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.5	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	3.6	[email protected]
7.5	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.5

3.1

HIGH

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

3.6

[email protected]

7.5

3.1

HIGH

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

3.6

[email protected]

OS Trackers for CVE-2022-3094

vendor	priority	summary	link
`alpine`	—	CVE-2022-3094: 1 source package rows (bind); 69 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 62.	https://security.alpinelinux.org/vuln/CVE-2022-3094
`debian`	not yet assigned	CVE-2022-3094 not yet assigned priority: Debian including 1 source packages (bind9), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-3094
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-3094
`suse`	medium	CVE-2022-3094 severity moderate: SUSE including 322 source package names (amazon/suse-sles-15-sp1-chost-byos-v20210304-hvm-ssd-x86_64, amazon/suse-sles-15-sp1-chost-byos-v20220127-hvm-ssd-x86_64, …), 948 product×package rows across 138 product lines (Image SLES15-SP3-BYOS-Azure, Image SLES15-SP3-BYOS-EC2-HVM, … (138 product lines)): Fixed 728, Known Affected 129, Will Not Fix 91.	https://www.suse.com/security/cve/CVE-2022-3094/
`ubuntu`	medium	CVE-2022-3094 medium priority: Ubuntu including 2 source packages (bind9, isc-dhcp), 16 status rows across 8 suites (bionic, focal, jammy, kinetic, lunar, trusty, upstream, xenial): not-affected 10, released 5, needs-triage 1.	https://ubuntu.com/security/CVE-2022-3094

Affected software / configurations for CVE-2022-3094

Vendor	Product	Version	Raw CPE
isc	bind	>= 9.16.0, < 9.16.37	cpe:2.3:a:isc:bind:::::-:::*
isc	bind	>= 9.18.0, < 9.18.11	cpe:2.3:a:isc:bind:::::-:::*
isc	bind	>= 9.19.0, < 9.19.9	cpe:2.3:a:isc:bind:::::-:::*
isc	bind	9.16.8	cpe:2.3:a:isc:bind:9.16.8:s1:::supported_preview:::*
isc	bind	9.16.11	cpe:2.3:a:isc:bind:9.16.11:s1:::supported_preview:::*
isc	bind	9.16.13	cpe:2.3:a:isc:bind:9.16.13:s1:::supported_preview:::*
isc	bind	9.16.14	cpe:2.3:a:isc:bind:9.16.14:s1:::supported_preview:::*
isc	bind	9.16.21	cpe:2.3:a:isc:bind:9.16.21:s1:::supported_preview:::*
isc	bind	9.16.32	cpe:2.3:a:isc:bind:9.16.32:s1:::supported_preview:::*
isc	bind	9.16.36	cpe:2.3:a:isc:bind:9.16.36:s1:::supported_preview:::*

References for CVE-2022-3094

URL	Tags
https://kb.isc.org/docs/cve-2022-3094	Vendor Advisory

URL

CVE-2022-3094 | An UPDATE message flood may cause named to exhaust all available memory

Exploit prediction scoring system (EPSS) score for CVE-2022-3094

Common vulnerability scoring system (CVSS) metrics for CVE-2022-3094

Weakness enumeration for CVE-2022-3094

OS Trackers for CVE-2022-3094

Affected software / configurations for CVE-2022-3094

References for CVE-2022-3094