LiveActive security incident?Get immediate response
CVE Record

CVE-2020-8619: A buffer boundary check assertion in rdataset.c can fail incorrectly during zone transfer

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.

MediumCVSS 4.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw can crash affected ISC BIND9 name servers in a narrow zone-transfer condition. It matters mainly for organizations running authoritative DNS on affected BIND versions. The public record does not indicate active exploitation, and the source describes abuse as unlikely because an attacker needs significant zone-content privileges.

Executive priority

Treat this as a targeted availability risk, not a broad internet-wide emergency. Patch affected authoritative DNS infrastructure through normal vulnerability management, faster where DNS availability is business-critical or zone administration is delegated to many users or systems.

Technical view

CVE-2020-8619 is an ISC BIND9 assertion failure in rdataset.c during zone transfer. Exposure requires affected versions and authoritative service for at least one zone containing an empty non-terminal entry with an asterisk character. Impact is denial of service, with CVSS 4.9 and high privileges required.

Likely exposure

Likely exposure is limited to authoritative ISC BIND9 deployments running 9.11.14-9.11.19, 9.16.0-9.16.3, 9.11.14-S1-9.11.19-S1, or 9.14.9-9.14.12. Recursive-only servers and deployments without the described zone-content condition are not indicated as affected by the provided description.

Exploitation context

The source bundle says exploitation would require permission to change zone content and introduce the triggering condition. It also says this vector is unlikely and easily traceable. CISA KEV is false in the provided data, so there is no source-backed evidence here of active exploitation.

Researcher notes

The key gating conditions are authoritative service, affected version range, and specific wildcard-related empty non-terminal zone content. The privilege requirement is high. Public sources in the bundle do not provide exploit details or active exploitation evidence; avoid assuming broader BIND exposure without validating deployment role and zone data.

Mitigation direction

  • Upgrade affected ISC BIND9 instances to fixed vendor or distribution packages.
  • Prioritize authoritative DNS servers before recursive-only DNS infrastructure.
  • Restrict zone-content modification privileges to trusted administrators and controlled automation.
  • Review vendor advisories from ISC and your operating-system distributor.
  • Monitor DNS service availability until remediation is complete.

Validation and detection

  • Inventory BIND9 versions across authoritative DNS servers.
  • Confirm whether each server provides authoritative service for any zone.
  • Review zone data for empty non-terminal entries containing an asterisk character.
  • Verify patched package versions against ISC or distribution advisories.
  • Check DNS service logs for assertion failures or unexpected named restarts.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-8619 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H1.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.9Medium
CVSS 3.1 vector shape for CVE-2020-8619Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ISCBIND99.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.12Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.