CVE-2020-8623
No exploitation reported by the sources we read.
- Published2020-08-21
- WeaknessCWE-617
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In BIND 9.10.0 -> 9.11.21, 9.12.0 -> 9.16.5, 9.17.0 -> 9.17.3, also affects 9.10.5-S1 -> 9.11.21-S1 of the BIND 9 Supported Preview Edition, An attacker that can reach a vulnerable system with a specially crafted query packet can trigger a crash. To be vulnerable, the system must: * be running BIND that was built with "--enable-native-pkcs11" * be signing one or more zones with an RSA key * be able to receive queries from a possible attacker
Timeline
dates in UTC- 2020-08-2121:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-8623?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-8623?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 9.x | ≥ 9.10.0, ≤ 9.11.21 | no fix published | NVD |
| 9.x | ≥ 9.12.1, ≤ 9.16.5 | no fix published | NVD |
| 9.17 | ≥ 9.17.0, ≤ 9.17.3 | no fix published | NVD |
| 9.10 | = 9.10.5 | no fix published | NVD |
| 9.11 | = 9.11.21 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 16.4 | = 16.04 | no fix published | NVD |
| 18.4 | = 18.04 | no fix published | NVD |
| 20.4 | = 20.04 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 9.0 | = 9.0 | no fix published | NVD |
| 10.0 | = 10.0 | no fix published | NVD |
4 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- kb.isc.orgVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- CNACVSS 3.17.5read 2026-10-23
- NVDCVSS 3.17.5read 2026-10-23
- NVDCVSS 2.04.3read 2026-10-23
- NVDweakness (CWE)CWE-617read 2026-10-23
- FIRST EPSSEPSS score6.6 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2020-08-21
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2020-8623?
Is CVE-2020-8623 actively exploited?
What is the CVSS score for CVE-2020-8623?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.