Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
  • Support the projectPage
Back

CVE-2019-6476

An error in QNAME minimization code can cause BIND to exit with an assertion failure

Description

A defect in code added to support QNAME minimization can cause named to exit with an assertion failure if a forwarder returns a referral rather than resolving the query. This affects BIND versions 9.14.0 up to 9.14.6, and 9.15.0 up to 9.15.4.

Timeline

  1. ID reserved

    By isc

  2. · 9 months later

    Published

  3. · 5 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2019-6476, by who scored it
Scored byCVSSScoreVector
iscCNA (assigner)3.1Medium5.9CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
3.0% · top 13% of all CVEs (10 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.9.

Affected products

  • ISC · BIND 9

    • affected 9.14.0 up to 9.14.6
    • affected 9.15.0 up to 9.15.4

What to do

Solution: Upgrade to the patched release most closely related to your current version of BIND: + BIND 9.14.7 + BIND 9.15.5

Workaround: ervers which have QNAME minimization turned on are potentially vulnerable to this defect if they are running an affected version of BIND. The vulnerability can be avoided by disabling QNAME minimization using "qname-minimization disabled;" in the global options section of named.conf (Note: the default value for the qname-minimization setting in the 9.14 and 9.15 branches is "relaxed". To make use of this workaround it must be explicitly disabled.)

References

3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2019-6476 badge
[![CVE-2019-6476](https://cveledger.app/badge/CVE-2019-6476.svg)](https://cveledger.app/cve/CVE-2019-6476)

Record last updated .