VDB

CVE-2022-2906

CVE-2022-2906 PUBLISHED CVSS 7.5 HIGH

Reported by isc · Published September 21, 2022

An attacker can leverage this flaw to gradually erode available memory to the point where named crashes for lack of resources. Upon restart the attacker would have to begin again, but nevertheless there is the potential to deny service.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
bindAlpine9.18.7-r0, 9.16.33-r0

Risk scores

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

Affected products

VendorProductVersions
ISCBIND9Open Source Branch 9.18 9.18.0 through versions before 9.18.7, Development Branch 9.19 9.19.0 through versions before 9.19.5
chainguardbind*
alpinebind0, 0
ISCBIND99.18, 9.19
wolfibind*

Timeline

  • Sep 20, 2022 CVE Published
  • Sep 22, 2022 EPSS Score (30 in total, the first dated here)
  • May 28, 2025 CVE Updated
  • Mar 10, 2026 Security Advisory (23 in total, the first dated here)
  • Jun 27, 2026 Coalition ESS Score
  • Nov 22, 2026 Distribution Patch (19 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2022-2906
vulnetix vdb fixes CVE-2022-2906

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2022-2906/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›