NVD / CVE Program· CNA isc

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

Noroxi assessment

Priority: Monitor (action score 34/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: 13.2% (FIRST EPSS); higher than 96.3% 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: bind (AlmaLinux:8) 32:9.11.36-11.el8_9; bind-chroot (AlmaLinux:8) 32:9.11.36-11.el8_9; bind-devel (AlmaLinux:8) 32:9.11.36-11.el8_9.

Low priority for now. Upgrade to bind (AlmaLinux:8) 32:9.11.36-11.el8_9; bind-chroot (AlmaLinux:8) 32:9.11.36-11.el8_9; bind-devel (AlmaLinux:8) 32:9.11.36-11.el8_9 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

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.

HighCVSS 7.5 · v3.1—No exploit Fix available

Published: Jan 26, 2023
Updated: Jun 17, 2026
EPSS: 13.2% · 96th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 4 / 30 · 13.2%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.5
CNA · isc: 7.5; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

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.

Vendor	Product	CPE
isc	bind	cpe:2.3:a:isc:bind

Affected versions

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

isc bind9.18.0 and later · before 9.18.11
isc bind9.19.0 and later · before 9.19.9
isc bind9.16.0 and later · before 9.16.37
isc bind9.16.11
isc bind9.16.13
isc bind9.16.14
isc bind9.16.21
isc bind9.16.32
isc bind9.16.36
isc bind9.16.8

Versions reported by the vendor

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

ISC BIND 9
- 9.16.0 and later · up to and including 9.16.36affected
- 9.18.0 and later · up to and including 9.18.10affected
- 9.19.0 and later · up to and including 9.19.8affected
- 9.16.8-S1 and later · up to and including 9.16.36-S1affected

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
AlmaLinux:8	bind	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-chroot	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-devel	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-export-devel	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-export-libs	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-libs	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-libs-lite	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-license	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-lite-devel	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-pkcs11	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-pkcs11-devel	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-pkcs11-libs	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-pkcs11-utils	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-sdb	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-sdb-chroot	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind-utils	before 32:9.11.36-11.el8_9	32:9.11.36-11.el8_9
AlmaLinux:8	bind9.16	before 32:9.16.23-0.14.el8	32:9.16.23-0.14.el8
AlmaLinux:8	bind9.16-chroot	before 32:9.16.23-0.14.el8	32:9.16.23-0.14.el8
AlmaLinux:8	bind9.16-devel	before 32:9.16.23-0.14.el8	32:9.16.23-0.14.el8
AlmaLinux:8	bind9.16-dnssec-utils	before 32:9.16.23-0.14.el8	32:9.16.23-0.14.el8
AlmaLinux:8	bind9.16-doc	before 32:9.16.23-0.14.el8	32:9.16.23-0.14.el8
AlmaLinux:8	bind9.16-libs	before 32:9.16.23-0.14.el8	32:9.16.23-0.14.el8
AlmaLinux:8	bind9.16-license	before 32:9.16.23-0.14.el8	32:9.16.23-0.14.el8
AlmaLinux:8	bind9.16-utils	before 32:9.16.23-0.14.el8	32:9.16.23-0.14.el8

+96

Same product

isc: all records

Other highest-scoring records for the same primary product.

CVE-2015-5477named in ISC BIND 9.x before 9.9.7-P2 and 9.10.x before 9.10.2-P3 allows remote attackers to cause a denial of service (REQUIRE assertion faKEV
90Now
CVE-2020-8617A logic error in code which checks TSIG validity can be used to trigger an assertion failure in tsig.c
60This week
CVE-2016-2776buffer.c in named in ISC BIND 9 before 9.9.9-P3, 9.10.x before 9.10.4-P3, and 9.11.x before 9.11.0rc3 does not properly construct responses,
60This week

Published before and after this one in the same product

← EarlierCVE-2022-38178Sep 21, 2022 · Memory leaks in EdDSA DNSSEC verification code
31Monitor
← EarlierCVE-2022-3080Sep 21, 2022 · BIND 9 resolvers configured to answer from stale cache with zero stale-answer-client-timeout may terminate unexpectedly
31Monitor
Later →CVE-2022-3488Jan 26, 2023 · named may terminate unexpectedly when processing ECS options in repeated responses to iterative queries
36Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
almalinux:bind	32:9.16.23-11.el9 · AlmaLinux:9	Package registry (OSV)
almalinux:bind-chroot	32:9.16.23-11.el9 · AlmaLinux:9	Package registry (OSV)
almalinux:bind-devel	32:9.16.23-11.el9 · AlmaLinux:9	Package registry (OSV)
almalinux:bind-dnssec-doc	32:9.16.23-11.el9 · AlmaLinux:9	Package registry (OSV)
almalinux:bind-dnssec-utils	32:9.16.23-11.el9 · AlmaLinux:9	Package registry (OSV)
almalinux:bind-doc	32:9.16.23-11.el9 · AlmaLinux:9	Package registry (OSV)
almalinux:bind-libs	32:9.16.23-11.el9 · AlmaLinux:9	Package registry (OSV)
almalinux:bind-license	32:9.16.23-11.el9 · AlmaLinux:9	Package registry (OSV)
almalinux:bind-utils	32:9.16.23-11.el9 · AlmaLinux:9	Package registry (OSV)
almalinux:bind9.16	32:9.16.23-0.14.el8 · AlmaLinux:8	Package registry (OSV)
almalinux:bind9.16-chroot	32:9.16.23-0.14.el8 · AlmaLinux:8	Package registry (OSV)
almalinux:python3-bind	32:9.16.23-11.el9 · AlmaLinux:9	Package registry (OSV)
alpine:bind	9.16.37-r0 · Alpine:v3.14	Package registry (OSV)
debian:bind9	1:9.18.11-1 · Debian:12	Package registry (OSV)
opensuse:bind	9.16.37-150400.5.17.1 · openSUSE:Leap 15.4	Package registry (OSV)
red hat:bind	32:9.16.23-11.el9 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:bind-chroot	32:9.16.23-11.el9 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:bind-debuginfo	32:9.16.23-11.el9 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:bind-debugsource	32:9.16.23-11.el9 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:bind-dnssec-doc	32:9.16.23-11.el9 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:bind-dnssec-utils	32:9.16.23-11.el9 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:bind-dnssec-utils-debuginfo	32:9.16.23-11.el9 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:bind-libs	32:9.16.23-11.el9 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:bind-libs-debuginfo	32:9.16.23-11.el9 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:bind-license	32:9.16.23-11.el9 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:bind-utils	32:9.16.23-11.el9 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:bind-utils-debuginfo	32:9.16.23-11.el9 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
suse:bind	9.16.37-150400.5.17.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4	Package 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.

Credits

All researchers

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

Rob SchulhofInfoblox for bringing this vulnerability to our attention.

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

Weakness class (CWE)

CWE-416 · Use After Free

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

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

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

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

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

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

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

References

kb.isc.org/docs/cve-2022-3094

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records