# CVE-2022-1183: Destroying a TLS session early causes assertion failure

> Attackers can cause a denial of service in BIND DNS servers configured for DNS over HTTPS by triggering an assertion failure during TLS session termination.

- **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:** 19 May 2022
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2022-1183, GHSA-wgcp-6p65-qv57, UBUNTU-CVE-2022-1183, USN-5429-1, openSUSE-SU-2024:12129-1

## What is CVE-2022-1183?

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

### Official description

On vulnerable configurations, the named daemon may, in some circumstances, terminate with an assertion failure. Vulnerable configurations are those that include a reference to http within the listen-on statements in their named.conf. TLS is used by both DNS over TLS (DoT) and DNS over HTTPS (DoH), but configurations using DoT alone are unaffected. Affects BIND 9.18.0 -> 9.18.2 and version 9.19.0 of the BIND 9.19 development branch.

Weakness: CWE-617 (Reachable Assertion)

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

It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bind` | openSUSE:Tumbleweed | All versions | 9.18.3-1.1 |

Products: Isc Bind, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500s Firmware, Netapp H700s Firmware.

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

Upgrade to a fixed version.

## Is CVE-2022-1183 being exploited?

There is no known exploitation of CVE-2022-1183 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-1183 and fix it if it is affected.

What it is: CVE-2022-1183 is a high-severity denial of service vulnerability in Isc Bind, published on 19 May 2022. 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-1183 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-1183/ (Markdown: https://insights.sbomify.com/CVE-2022-1183/index.md)
```

## Sources

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

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