BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2020
CVE-2020-8619High confidence

A buffer boundary check assertion in rdataset.c can fail incorrectly during zone transfer

ISC · BIND9

4.9MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 2.10% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs ISC BIND9 and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainbindVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.9.16.4-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainbindVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.9.16.4-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainbindVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.9.16.4-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcebind9Vendor fix publishedDebian records a fixed source-package version for this release.1:9.16.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcebind9Vendor fix publishedDebian records a fixed source-package version for this release.1:9.16.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcebind9Vendor fix publishedDebian records a fixed source-package version for this release.1:9.16.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcebind9Vendor fix publishedDebian records a fixed source-package version for this release.1:9.16.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2020-8619 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitybind: asterisk character in an empty non-terminal can cause an assertion failure in rbtdb.c
171 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • bind-32:9.11.20-5.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • bind-32:9.11.20-5.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • bind-32:9.11.20-5.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • bind-32:9.11.20-5.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • bind-chroot-32:9.11.20-5.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • bind-chroot-32:9.11.20-5.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • bind-chroot-32:9.11.20-5.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • bind-chroot-32:9.11.20-5.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • bind-debuginfo-32:9.11.20-5.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • bind-debuginfo-32:9.11.20-5.el8.i686 as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • bind-debuginfo-32:9.11.20-5.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)
  • bind-debuginfo-32:9.11.20-5.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)
Summary
A flaw was found in bind when an asterisk character is present in an empty non-terminal location within the DNS graph. This flaw could trigger an assertion failure, causing bind to crash. The highest threat from this vulnerability is to system availability.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2020-29467

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

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.

What

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.

Why

The product does not release or incorrectly releases a resource before it is made available for re-use.

How

An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may disrupt the affected service.

What

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.

Why

The product does not release or incorrectly releases a resource before it is made available for re-use.

How

An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Resource Shutdown or Release → disrupt the affected service
Attack surface
Network
Privileges required
High: elevated access is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-404 ↗

CWE-404: Improper Resource Shutdown or Release. The product does not release or incorrectly releases a resource before it is made available for re-use.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkDenial of serviceCWE-404
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20200624Security Bulletin 24 Jun 2020

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 24 Jun 2020, published on 24 June 2020. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2020-AVI-382Multiples vulnérabilités dans BIND

De multiples vulnérabilités ont été découvertes dans BIND. Elles permettent à un attaquant de provoquer un déni de service à distance.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2020-006937ISC BIND におけるリソースの不適切なシャットダウンおよびリリースに関する脆弱性

ISC BIND には、リソースの不適切なシャットダウンおよびリリースに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
BIND9: 9.11.14 through versions before 9.11.20, 9.16.0 through versions before 9.16.4, 9.11.14-S1 through versions before 9.11.20-S1, 9.14.9 through versions 9.14.12
Fixed
Action
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 17 Jun 2020 · Last source change 17 Sept 2024, 03:28 UTC · CWE-404 · Improper Resource Shutdown or Release

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2020-29467
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    9.11.14 through versions before 9.11.20; 9.16.0 through versions before 9.16.4; 9.11.14-S1 through versions before 9.11.20-S1; 9.14.9 through versions 9.14.12 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    9.11.14 through versions before 9.11.20; 9.16.0 through versions before 9.16.4; 9.11.14-S1 through versions before 9.11.20-S1; 9.14.9 through versions 9.14.12 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2020-29467↗Red Hat Product Security security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2020-8619 · cve.blacktree.nl