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

> Trusted clients can cause a denial of service in BIND by flooding dynamic DNS updates, exhausting server memory.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jan 2023
- **Updated:** 1 Apr 2025
- **Also known as:** ALPINE-CVE-2022-3094, ALSA-2023:7177, AZL-13204, CLSA-2024-1718289878, CLSA-2024-1718794440, CLSA-2025-1742474086, CLSA-2025-1762957104, CLSA-2025-1762957404, DEBIAN-CVE-2022-3094, GHSA-8f7f-g9cj-hq6g, RHSA-2023:7177, RHSA-2024:1406, SUSE-SU-2023:0427-1, UBUNTU-CVE-2022-3094

## What is CVE-2022-3094?

CVE-2022-3094 is a high-severity denial of service vulnerability in Isc Bind, published on 25 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-416 (Use After Free), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2022-3094?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bind` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-chroot` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-devel` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-export-devel` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-export-libs` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-libs` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-libs-lite` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-license` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-lite-devel` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-pkcs11` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-pkcs11-devel` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-pkcs11-libs` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-pkcs11-utils` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-sdb` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-sdb-chroot` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind-utils` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `python3-bind` | AlmaLinux:8 | All versions | 32:9.11.36-11.el8_9 |
| `bind` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-chroot` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-export-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-libs` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-libs-lite` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-libs-lite-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-license` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-lite-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-pkcs11` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-pkcs11-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-pkcs11-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-pkcs11-libs` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-pkcs11-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-pkcs11-utils` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-pkcs11-utils-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-sdb` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-sdb-chroot` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-sdb-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |
| `bind-utils` | Red Hat:enterprise_linux:8::appstream | All versions | 32:9.11.36-11.el8_9 |

Products: Isc Bind.

## How do I fix CVE-2022-3094?

Upgrade to a fixed version.

## Is CVE-2022-3094 being exploited?

There is no known exploitation of CVE-2022-3094 in the wild and no public exploit code.

## Other vulnerabilities in Isc Bind

- [CVE-2008-0122](https://insights.sbomify.com/CVE-2008-0122/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0010](https://insights.sbomify.com/CVE-2001-0010/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0011](https://insights.sbomify.com/CVE-2001-0011/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0013](https://insights.sbomify.com/CVE-2001-0013/): Memory corruption in n/a (critical 10.0)
- [CVE-2000-1029](https://insights.sbomify.com/CVE-2000-1029/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3094 and fix it if it is affected.

What it is: CVE-2022-3094 is a high-severity denial of service vulnerability in Isc Bind, published on 25 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3094 in the wild and no public exploit code.

Affected product: Isc Bind. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-3094/ (Markdown: https://insights.sbomify.com/CVE-2022-3094/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3094
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3094
- OSV: https://osv.dev/vulnerability/CVE-2022-3094

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-3094/
Summaries are generated and may contain mistakes; the official description above is the record.