Vulnerability · CVE-2020-8619
In ISC BIND9 versions BIND 9.11.14 -> 9.11.19, BIND 9.14.9 -> 9.14.12, BIND 9.16.0 -> 9.16.3, BIND Supported Preview Edition 9.11.14-S1 -> 9.11.19-S1: Unless a nameserver is provid
Published Jun 17, 2020 · catalog updated Oct 26, 2026 · In ISC BIND9 versions
Last checked Nov 6, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2020-8619. EPSS is 2.15%. Act only if a listed version of In ISC BIND9 versions is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (In ISC BIND9 versions).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium4.9
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 2.15%
- Remediation
- Advisory link
- Affected products
- Alpine:v3.10 bind · Alpine:v3.11 bind · Alpine:v3.12 bind · Alpine:v3.13 bind · Alpine:v3.14 bind · Alpine:v3.15 bind
In ISC BIND9 versions BIND 9.11.14 -> 9.11.19, BIND 9.14.9 -> 9.14.12, BIND 9.16.0 -> 9.16.3, BIND Supported Preview Edition 9.11.14-S1 -> 9.11.19-S1: Unless a nameserver is providing authoritative service for one or more zones and at least one zone contains an empty non-terminal entry containing an asterisk ("*") character, this defect cannot be encountered. A would-be attacker who is allowed to change zone content could theoretically introduce such a record in order to exploit this condition to cause denial of service, though we consider the use of this vector unlikely because any such attack would require a significant privilege level and be easily traceable.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Alpine:v3.10 bind9.11.14 → 9.16.4-r0
- Alpine:v3.11 bind9.11.14 → 9.16.4-r0
- Alpine:v3.12 bind9.11.14 → 9.16.4-r0
- Alpine:v3.13 bind9.11.14 → 9.16.4-r0
- Alpine:v3.14 bind9.11.14 → 9.16.4-r0
- Alpine:v3.15 bind9.11.14 → 9.16.4-r0
- Alpine:v3.16 bind9.11.14 → 9.16.4-r0
- Alpine:v3.17 bind9.11.14 → 9.16.4-r0
- Alpine:v3.18 bind9.11.14 → 9.16.4-r0
- Alpine:v3.19 bind9.11.14 → 9.16.4-r0
- Alpine:v3.20 bind9.11.14 → 9.16.4-r0
- Alpine:v3.21 bind9.11.14 → 9.16.4-r0
How to fix CVE-2020-8619
Upgrade
CVE-2020-8619 lists a fix boundary at 9.16.4-r0. Compare the installed build with that boundary before you change production.
Version check
Seen in 9.11.14 → 9.16.4-r0 · 5 other packages on the advisory
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2020-8619. EPSS is 2.15%. Act only if a listed version of In ISC BIND9 versions is installed.
Which versions are affected?
Compare what you have installed with 9.11.14 → 9.16.4-r0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 2.15%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Jun 17, 2020 · Trivy Vulnerability DB
Detected
In ISC BIND9 versions BIND 9.11.14 -> 9.11.19, BIND 9.14.9 -> 9.14.12, BIND 9.16.0 -> 9.16.3, BIND Supported Preview Edition 9.11.14-S1 -> 9.11.19-S1: Unless a nameserver is providing authoritative service for one or more zones and at least one zone contains an empty non-terminal entry containing an asterisk ("*") character, this defect cannot be encountered. A would-be attacker who is allowed to
Oct 26, 2026 · Trivy Vulnerability DB
Fix available
bind fixed in 9.16.4-r0; bind fixed in 9.16.4-r0; bind fixed in 9.16.4-r0; bind fixed in 9.16.4-r0
Oct 26, 2026 · Trivy Vulnerability DB
Fix available
bind fixed in 9.16.4-r0
Oct 26, 2026 · Trivy Vulnerability DB
Updated
In ISC BIND9 versions BIND 9.11.14 -> 9.11.19, BIND 9.14.9 -> 9.14.12, BIND 9.16.0 -> 9.16.3, BIND Supported Preview Edition 9.11.14-S1 -> 9.11.19-S1: Unless a nameserver is providing authoritative service for one or more zones and at least one zone contains an empty non-terminal entry containing an asterisk ("*") character, this defect cannot be encountered. A would-be attacker who is allowed to
Sources
- CVE.orgVulnerability recordCVE-2020-8619
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2020-8619
30-day exploitation probability 2.15%
first.org - Trivy Vulnerability DBPackage advisoryALPINE-CVE-2020-8619
In ISC BIND9 versions BIND 9.11.14 -> 9.11.19, BIND 9.14.9 -> 9.14.12, BIND 9.16.0 -> 9.16.3, BIND Supported Preview Edition 9.11.14-S1 -> 9.11.19-S1: Unless a nameserver is providing authoritative service for one or more zones and at least one zone contains an empty non-terminal
osv.dev
References
Freshness
Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 6, 2026
- CVE.orgOct 26, 2026
- Trivy Vulnerability DBOct 26, 2026