dbcve.org
BindApplication · Isc

CVE-2022-1183

HIGH · 7.5 CVSS v3.1 Published 2022-05-19
Fix available
A fix is available. Upgrade to after 9.18.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A denial of service vulnerability in BIND 9's named daemon allows an attacker to cause the server to terminate with an assertion failure. The vulnerability is triggered when the server configuration includes an http reference in listen-on statements, specifically affecting DNS over HTTPS (DoH) configurations. DoT-only configurations are not affected.

MitigationUpgrade BIND 9 to version 9.18.3 or later (9.19.2 or later for the 9.19 branch). Alternatively, if upgrading is not immediately possible, consider disabling DoH and using DoT only until the upgrade can be performed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BindApplication
Affected:>= 9.18.0, <= 9.18.2= 9.19.0
H410c FirmwareOperating system
Affected:all versions
H300s FirmwareOperating system
Affected:all versions
H500s FirmwareOperating system
Affected:all versions
H700s FirmwareOperating system
Affected:all versions
H410s FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check BIND version
    Run 'named -v' or 'named -V' to determine the installed version of the BIND named daemon
    Affected if The version is 9.18.0, 9.18.1, 9.18.2, or 9.19.0
  2. Identify DoH configuration in named.conf
    Search the named.conf file (typically in /etc/bind/named.conf or /etc/named.conf) for 'listen-on' statements containing 'http' - look for patterns like 'listen-on port 443 http' or similar DoH-related configuration
    Affected if The listen-on configuration includes an http statement, indicating DoH is enabled
  3. Verify DoH is actually in use
    Check if the http listener is actively configured and not commented out - review any 'http' type listeners in the options or server blocks of the BIND configuration
    Affected if An active http listener is configured in the BIND configuration files (DoT-only setups are not affected)
  4. Check NetApp firmware version (if applicable)
    For NetApp H300s, H410c, H410s, H500s, H700s systems, check the firmware version through the NetApp documentation or system management interface
    Affected if Running any firmware version on the listed NetApp models that includes the vulnerable BIND version

You are affected if running BIND 9.18.0-9.18.2 or 9.19.0 AND have DoH (http listener) enabled in your listen-on configuration; DoT-only configurations are not vulnerable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 9.18.2
Interim mitigation

Upgrade BIND 9 to version 9.18.3 or later (9.19.2 or later for the 9.19 branch). Alternatively, if upgrading is not immediately possible, consider disabling DoH and using DoT only until the upgrade can be performed.

Recommended fix High confidence

BIND 9.18.3+ or BIND 9.19.1+ (stable branch)

  1. 1. Identify all BIND9 servers running versions 9.18.0, 9.18.1, 9.18.2, or 9.19.0 in your environment
  2. 2. Check the current configuration in named.conf for any 'http' references within listen-on statements (e.g., listen-on port 53 http { any; };)
  3. 3. Schedule a maintenance window for the BIND9 upgrade
  4. 4. Download the fixed BIND9 version (9.18.3 or later for the 9.18 branch, or 9.19.1 or later for the 9.19 branch) from ISC
  5. 5. Stop the named service on the affected servers: systemctl stop named
  6. 6. Install the updated BIND9 package using your system's package manager
  7. 7. Verify the installed version matches a fixed release: named -v
  8. 8. Start the named service: systemctl start named
Caveat Minor: Review release notes for any behavioral changes between 9.18.x versions; generally backward compatible for security patches

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bind Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1183 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-1183 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data