LiveActive security incident?Get immediate response
CVE Record

CVE-2020-8624: update-policy rules of type "subdomain" are enforced incorrectly

In BIND 9.9.12 -> 9.9.13, 9.10.7 -> 9.10.8, 9.11.3 -> 9.11.21, 9.12.1 -> 9.16.5, 9.17.0 -> 9.17.3, also affects 9.9.12-S1 -> 9.9.13-S1, 9.11.3-S1 -> 9.11.21-S1 of the BIND 9 Supported Preview Edition, An attacker who has been granted privileges to change a specific subset of the zone's content could abuse these unintended additional privileges to update other contents of the zone.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw affects certain BIND 9 DNS servers where administrators allowed limited dynamic zone updates. A user or system already trusted to update one part of a DNS zone could change more zone content than intended. Business impact is mainly DNS integrity, not direct server takeover.

Executive priority

Prioritize remediation for authoritative DNS servers that use delegated dynamic updates. The issue is medium severity, but DNS record integrity can affect service routing, mail delivery, and trust in public-facing infrastructure.

Technical view

BIND 9 incorrectly enforced update-policy rules of type subdomain across listed affected release ranges. With network access and low privileges already granted for dynamic updates, an attacker could exceed the intended zone-update boundary and modify additional records. CVSS 3.1 is 4.3 with integrity impact only.

Likely exposure

Exposure is most likely on authoritative BIND 9 deployments using dynamic DNS updates with update-policy subdomain rules. BIND installations without those delegated update permissions are less likely to be affected in practice, even if running an affected version.

Exploitation context

The source bundle does not show CISA KEV listing or public active exploitation evidence. Abuse requires an already-authorized updater for part of a zone, making this an insider, compromised credential, or delegated automation risk.

Researcher notes

Focus analysis on configured update-policy semantics, not only package version. The attacker model requires pre-existing update privileges. Evidence in the provided bundle supports integrity impact and vendor updates, but not unauthenticated exploitation or active exploitation.

Mitigation direction

  • Apply fixed BIND packages from ISC or the relevant operating-system vendor advisory.
  • Review vendor guidance for exact fixed versions in your distribution or appliance.
  • Restrict dynamic DNS update keys to the minimum required scope.
  • Disable dynamic updates where operationally unnecessary.
  • Review update-policy rules of type subdomain for unintended trust boundaries.
  • Monitor DNS zone changes for records outside delegated areas.

Validation and detection

  • Inventory BIND 9 versions against the affected ranges in the CVE record.
  • Check named configuration for update-policy rules using type subdomain.
  • List principals or TSIG keys allowed to perform dynamic updates.
  • Verify vendor security updates were installed on DNS servers and appliances.
  • Review zone journals or audit logs for unexpected record changes.
  • Confirm delegated update accounts cannot modify records outside intended subdomains.
Prepared
Confidence
high
Sources
9

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-8624 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.3 (3.1)
Known Exploited
No
Published

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

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
9Source 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.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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.9.12, unspecified, 9.10.7, unspecified, 9.11.3, unspecified, 9.12.1, unspecified, 9.17.0, unspecified, 9.9.12-S1, unspecified, 9.11.3-S1, unspecifiedListed
Weakness

CWE details

No CWE listed

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