An error in QNAME minimization code can cause BIND to exit with an assertion failure
Published Oct 17, 2019
7.5
HIGHCVSS 3.1
EPSS 2.91%
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.
Affected products
-
- Version 9.14.0 up to 9.14.6StatusaffectedConstraints-
- Version 9.15.0 up to 9.15.4StatusaffectedConstraints-
- Version
No data.
Red Hat Enterprise Linux 5
bind
Not affected
Red Hat Enterprise Linux 6
bind
Not affected
Red Hat Enterprise Linux 7
bind
Not affected
Red Hat Enterprise Linux 8
bind
Not affected
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 5 | bind | Not affected | n/a |
| Red Hat Enterprise Linux 6 | bind | Not affected | n/a |
| Red Hat Enterprise Linux 7 | bind | Not affected | n/a |
| Red Hat Enterprise Linux 8 | bind | Not affected | n/a |
No package ranges for this CVE.
Remediation
Vendor solution
Upgrade to the patched release most closely related to your current version of BIND: + BIND 9.14.7 + BIND 9.15.5
Red Hat statement
This flaw did not affect the versions of bind shipped with Red Hat Enterprise Linux 6, 7 and 8.
Metrics
No CVSS v4.0 score for this CVE.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
1 other source (CVE.org) ▾
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
AV:N/AC:L/Au:N/C:N/I:N/A:P
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
- EPSS v4
Percentile over time
- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
- EPSS v4
Table of values (15 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 2.91% (0.02907) | 86.49th | v5 (v2026.06.15) |
| Jun 15, 2026 | 3.58% (0.03580) | 87.87th | v5 (v2026.06.15) |
| Mar 30, 2025 | 1.35% (0.01353) | 78.33th | v4 (v2025.03.14) |
| Mar 29, 2025 | 4.67% (0.04672) | 81.83th | v4 (v2025.03.14) |
| Jul 20, 2024 | 0.26% (0.00257) | 65.85th | v3 (v2023.03.01) |
| Mar 8, 2024 | 0.26% (0.00257) | 64.77th | v3 (v2023.03.01) |
| Sep 3, 2023 | 0.26% (0.00257) | 62.77th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.16% (0.00156) | 50.12th | v3 (v2023.03.01) |
| Mar 6, 2023 | 0.95% (0.00954) | 36.37th | v2 (v2022.01.01) |
| Apr 1, 2022 | 0.95% (0.00954) | 32.50th | v2 (v2022.01.01) |
| Feb 4, 2022 | 5.74% (0.05736) | 77.22th | v2 (v2022.01.01) |
| Feb 3, 2022 | 3.63% (0.03630) | 71.73th | v5 (v2026.06.15) |
| Jan 6, 2022 | 3.63% (0.03630) | 71.48th | v1 |
| Sep 1, 2021 | 0.83% (0.00833) | 57.50th | v1 |
| Apr 14, 2021 | 0.83% (0.00833) | 0.00th | v1 |
References (7)
- https://access.redhat.com/security/cve/CVE-2019-6476 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1762957 Issue Tracking
- https://kb.isc.org/docs/cve-2019-6476 x_refsource_CONFIRMThird Party Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2019-6476
- https://security.netapp.com/advisory/ntap-20191024-0004/ x_refsource_CONFIRM
- https://support.f5.com/csp/article/K42238532?utm_source=f5support&%3Butm_medium=RSS x_refsource_CONFIRM
- https://www.cve.org/CVERecord?id=CVE-2019-6476
| Link | Providers | Tags |
|---|---|---|
| https://access.redhat.com/security/cve/CVE-2019-6476 | Vendor Advisory | |
| https://bugzilla.redhat.com/show_bug.cgi?id=1762957 | Issue Tracking | |
| https://kb.isc.org/docs/cve-2019-6476 | x_refsource_CONFIRMThird Party Advisory | |
| https://nvd.nist.gov/vuln/detail/CVE-2019-6476 | ||
| https://security.netapp.com/advisory/ntap-20191024-0004/ | x_refsource_CONFIRM | |
| https://support.f5.com/csp/article/K42238532?utm_source=f5support&%3Butm_medium=RSS | x_refsource_CONFIRM | |
| https://www.cve.org/CVERecord?id=CVE-2019-6476 |
Change history (0)
No recorded changes yet.