CVE-2020-8619 [Medium] | Denial of Service in 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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	6.93%	2.09%	-4.84%
2	2025-12-28	7.32%	6.93%	-0.39%
3	2025-12-27	—	7.32%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

6.93%

2.09%

-4.84%

2025-12-28

7.32%

6.93%

-0.39%

2025-12-27

—

7.32%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.9	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.2	3.6	[email protected]
4.9	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.2	3.6	[email protected]
4.0	2.0	MEDIUM	`AV:N/AC:L/Au:S/C:N/I:N/A:P` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:S) A single authentication is required. Confidentiality impact (C:N) No confidentiality impact. Integrity impact (I:N) No integrity impact. Availability impact (A:P) Partial availability impact.	8.0	2.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.9

3.1

MEDIUM

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.2

3.6

[email protected]

4.9

3.1

MEDIUM

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.2

3.6

[email protected]

4.0

2.0

MEDIUM

AV:N/AC:L/Au:S/C:N/I:N/A:P Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:S): A single authentication is required.
Confidentiality impact (C:N): No confidentiality impact.
Integrity impact (I:N): No integrity impact.
Availability impact (A:P): Partial availability impact.

8.0

2.9

[email protected]

OS Trackers for CVE-2020-8619

vendor	priority	summary	link
`alpine`	medium	CVE-2020-8619: 1 source package rows (bind); 19 state rows across 10 repos (3.10-main, 3.11-main, 3.12-main, 3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 14, open 5.	https://security.alpinelinux.org/vuln/CVE-2020-8619
`debian`	not yet assigned	CVE-2020-8619 not yet assigned priority: Debian including 1 source packages (bind9), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2020-8619
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2020-8619
`suse`	medium	CVE-2020-8619 severity moderate: SUSE including 504 source package names (0.1.0:sysuser-shadow-2.0-4.2.8, 0.1.75:sysuser-shadow-2.0-4.2.8, …), 761 product×package rows across 195 product lines (Container bci/bci-init, Container bci/dotnet-aspnet, … (195 product lines)): Fixed 515, Known Affected 157, Known Not Affected 89.	https://www.suse.com/security/cve/CVE-2020-8619/
`ubuntu`	medium	CVE-2020-8619 medium priority: Ubuntu including 1 source packages (bind9), 6 status rows across 6 suites (bionic, eoan, focal, trusty, upstream, xenial): not-affected 4, released 2.	https://ubuntu.com/security/CVE-2020-8619

Affected software / configurations for CVE-2020-8619

Vendor	Product	Version	Raw CPE
isc	bind	>= 9.11.14, <= 9.11.19	cpe:2.3:a:isc:bind::::::::
isc	bind	>= 9.11.14-s1, <= 9.11.19-s1	cpe:2.3:a:isc:bind:::::preview:::*
isc	bind	>= 9.14.9, <= 9.14.12	cpe:2.3:a:isc:bind::::::::
isc	bind	>= 9.16.0, <= 9.16.3	cpe:2.3:a:isc:bind::::::::
fedoraproject	fedora	31	cpe:2.3:o:fedoraproject:fedora:31:::::::*
fedoraproject	fedora	32	cpe:2.3:o:fedoraproject:fedora:32:::::::*
opensuse	leap	15.1	cpe:2.3:o:opensuse:leap:15.1:::::::*
opensuse	leap	15.2	cpe:2.3:o:opensuse:leap:15.2:::::::*
debian	debian_linux	10.0	cpe:2.3:o:debian:debian_linux:10.0:::::::*
canonical	ubuntu_linux	20.04	cpe:2.3:o:canonical:ubuntu_linux:20.04::::lts:::
netapp	steelstore_cloud_integrated_storage	—	cpe:2.3:a:netapp:steelstore_cloud_integrated_storage:-:::::::*

References for CVE-2020-8619

URL	Tags
http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00041.html	Mailing List Third Party Advisory
http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00044.html	Mailing List Third Party Advisory
https://kb.isc.org/docs/cve-2020-8619	Vendor Advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CNFTTYJ5JJJJ6QG3AHXJGDIIEYMDFWFW/
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EIOXMJX4N3LBKC65OXNBE52W4GAS7QEX/
https://security.netapp.com/advisory/ntap-20200625-0003/	Third Party Advisory
https://usn.ubuntu.com/4399-1/	Third Party Advisory
https://www.debian.org/security/2020/dsa-4752	Third Party Advisory

URL

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

Exploit prediction scoring system (EPSS) score for CVE-2020-8619

Common vulnerability scoring system (CVSS) metrics for CVE-2020-8619

Weakness enumeration for CVE-2020-8619

OS Trackers for CVE-2020-8619

Affected software / configurations for CVE-2020-8619

References for CVE-2020-8619