ISC BIND 9
87 vulnérabilités publiées citent ce produit.
Tel que les CNA l’écrivent dans leurs fiches CVE (éditeur et produit) ; les versions sont les leurs.
| CVE | Versions vulnérables | Titre | Sévérité | Publiée | EPSS | Exploitation |
|---|---|---|---|---|---|---|
| CVE-2026-97313 | 9.16.0 – 9.18.50 ; 9.20.0 – 9.20.29 ; 9.21.0 – 9.21.26 ; … | Specific RPZ configurations and query patterns may result in an unexpected exit | HIGH 7.5 | 0.4 % | ||
| CVE-2026-96888 | 9.16.0 – 9.18.50 ; 9.20.0 – 9.20.29 ; 9.21.0 – 9.21.26 ; … | Named may terminate unexpectedly when a redirect zone is used with strict QNAME minimization | HIGH 7.5 | 0.5 % | ||
| CVE-2026-94300 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.29 ; 9.21.0 – 9.21.26 ; … | Concurrent GSS-TSIG messages corrupt memory | HIGH 8.1 | 1.0 % | ||
| CVE-2026-19630 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.29 ; 9.21.0 – 9.21.26 ; … | Amplified resource exhaustion in inbound message processing | HIGH 7.5 | 0.4 % | ||
| CVE-2026-77119 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.27 ; 9.21.0 – 9.21.25 ; … | NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets | MEDIUM 5.9 | 0.2 % | ||
| CVE-2026-75029 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.27 ; 9.21.0 – 9.21.25 ; … | Message parser retains every identical singleton RDATA, enabling wire-to-work amplification | MEDIUM 5.3 | 0.5 % | ||
| CVE-2026-19668 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.27 ; 9.21.0 – 9.21.25 ; … | Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching | MEDIUM 5.3 | 0.5 % | ||
| CVE-2026-19033 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.27 ; 9.21.0 – 9.21.25 ; … | Unauthenticated IXFR deltas are applied to the live zone before TSIG verification | MEDIUM 6.5 | 0.2 % | ||
| CVE-2026-80274 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.27 ; 9.21.0 – 9.21.25 ; … | Validating resolver can abort while caching a mismatched NOQNAME proof | HIGH 7.5 | 0.6 % | ||
| CVE-2026-76163 | 9.20.0 – 9.20.27 ; 9.21.0 – 9.21.25 ; 9.20.9-S1 – 9.20.27-S1 | named aborts on a TKEY query when the user configuration has no global options statement | HIGH 7.5 | 0.6 % | ||
| CVE-2026-19666 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.27 ; 9.21.0 – 9.21.25 ; … | Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path | HIGH 7.5 | 0.6 % | ||
| CVE-2026-81563 | 9.18.0 – 9.18.50 ; 9.20.0 – 9.20.27 ; 9.21.0 – 9.21.25 ; … | SVCB AliasMode additional-data error leaks qpcache references | HIGH 7.5 | 0.6 % | ||
| CVE-2026-78301 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.27 ; 9.21.0 – 9.21.25 ; … | Out-of-zone database nodes can become authoritative zone cuts | MEDIUM 5.8 | 0.2 % | ||
| CVE-2026-77692 | 9.20.0 – 9.20.27 ; 9.21.0 – 9.21.25 ; 9.20.9-S1 – 9.20.27-S1 | Unauthenticated remote crash of named via a single DoH SIG(0) request | HIGH 7.5 | 6.6 % | ||
| CVE-2026-19941 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.27 ; 9.21.0 – 9.21.25 ; … | checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof | MEDIUM 5.9 | 0.2 % | ||
| CVE-2026-19662 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.27 ; 9.11.3-S1 – 9.18.50-S1 ; … | qpcache NOQNAME proof use-after-free crashes recursive resolver | MEDIUM 5.9 | 0.5 % | ||
| CVE-2026-19667 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.27 ; 9.21.0 – 9.21.25 ; … | Remote assertion failure via 16-bit length truncation in `dns_ncache_add()` | HIGH 7.5 | 0.6 % | ||
| CVE-2026-81736 | 9.18.0 – 9.18.50 ; 9.20.0 – 9.20.27 ; 9.21.0 – 9.21.25 ; … | Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees | HIGH 7.5 | 0.6 % | ||
| CVE-2026-13321 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.24 ; 9.21.0 – 9.21.23 ; … | DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field | HIGH 8.6 | 0.2 % | ||
| CVE-2026-13204 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.24 ; 9.21.0 – 9.21.23 ; … | Unexpected exit in certain situations with NSEC and NSEC3 both present | HIGH 7.5 | 0.5 % | ||
| CVE-2026-12617 | 9.18.0 – 9.18.50 ; 9.20.0 – 9.20.24 ; 9.18.11-S1 – 9.18.50-S1 ; … | Record ordering based unexpected exit with CNAME or DNAME | HIGH 7.5 | 0.5 % | ||
| CVE-2026-11721 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.24 ; 9.21.0 – 9.21.23 ; … | Cache poisoning possible with label count discrepancy, RRSIG, and wildcards | HIGH 7.5 | 0.4 % | ||
| CVE-2026-11622 | 9.11.0 – 9.18.50 ; 9.20.0 – 9.20.24 ; 9.21.0 – 9.21.23 ; … | Potential memory usage beyond configured limits | HIGH 7.5 | 0.5 % | ||
| CVE-2026-11605 | 9.20.0 – 9.20.24 ; 9.21.0 – 9.21.23 ; 9.20.9-S1 – 9.20.24-S1 | Unnecessary validation of DNSSEC signed records | HIGH 7.5 | 0.7 % | ||
| CVE-2026-11331 | 9.16.0 – 9.18.50 ; 9.20.0 – 9.20.24 ; 9.21.0 – 9.21.23 ; … | Potential wildcard CNAME RPZ policy bypass | HIGH 7.5 | 0.4 % | ||
| CVE-2026-10822 | 9.18.0 – 9.18.50 ; 9.20.0 – 9.20.24 ; 9.21.0 – 9.21.23 ; … | Key Record using PRIVATEDNS algorithm may lead to unexpected exit | MEDIUM 6.5 | 0.4 % | ||
| CVE-2026-10723 | 9.18.0 – 9.18.50 ; 9.20.0 – 9.20.24 ; 9.21.0 – 9.21.23 ; … | Incorrect acceptance of NSEC3 records | MEDIUM 6.8 | 0.3 % | ||
| CVE-2026-5950 | 9.18.36 – 9.18.48 ; 9.20.8 – 9.20.22 ; 9.21.7 – 9.21.21 ; … | Unbounded resend loop in BIND 9 resolver | MEDIUM 5.3 | 0.7 % | ||
| CVE-2026-5947 | 9.20.0 – 9.20.22 ; 9.21.0 – 9.21.21 ; 9.20.9-S1 – 9.20.22-S1 | SIG(0) validation during query flood may lead to undefined behavior | HIGH 7.5 | 1.4 % | ||
| CVE-2026-5946 | 9.11.0 – 9.16.50 ; 9.18.0 – 9.18.48 ; 9.20.0 – 9.20.22 ; … | Invalid handling of CLASS != IN | HIGH 7.5 | 1.9 % | ||
| CVE-2026-3593 | 9.20.0 – 9.20.22 ; 9.21.0 – 9.21.21 ; 9.20.9-S1 – 9.20.22-S1 | Heap use-after-free vulnerability in BIND 9 DNS-over-HTTPS implementation | CRITICAL 9.8 | 1.5 % | ||
| CVE-2026-3592 | 9.11.0 – 9.16.50 ; 9.18.0 – 9.18.48 ; 9.20.0 – 9.20.22 ; … | Amplification vulnerabilities via self-pointed glue records | MEDIUM 5.3 | 0.4 % | ||
| CVE-2026-3039 | 9.0.0 – 9.16.50 ; 9.18.0 – 9.18.48 ; 9.20.0 – 9.20.22 ; … | BIND 9 server memory exhaustion during GSS-API TKEY negotiation | HIGH 7.5 | 1.1 % | ||
| CVE-2026-3591 | 9.20.0 – 9.20.20 ; 9.21.0 – 9.21.19 ; 9.20.9-S1 – 9.20.20-S1 | A stack use-after-return flaw in SIG(0) handling code may enable ACL bypass | MEDIUM 5.4 | 0.4 % | ||
| CVE-2026-3119 | 9.20.0 – 9.20.20 ; 9.21.0 – 9.21.19 ; 9.20.9-S1 – 9.20.20-S1 | Authenticated query containing a TKEY record may cause named to terminate unexpectedly | MEDIUM 6.5 | 0.6 % | ||
| CVE-2026-3104 | 9.20.0 – 9.20.20 ; 9.21.0 – 9.21.19 ; 9.20.9-S1 – 9.20.20-S1 | Memory leak in code preparing DNSSEC proofs of non-existence | HIGH 7.5 | 0.7 % | ||
| CVE-2026-1519 | 9.11.0 – 9.16.50 ; 9.18.0 – 9.18.46 ; 9.20.0 – 9.20.20 ; … | Excessive NSEC3 iterations cause high CPU load during insecure delegation validation | HIGH 7.5 | 1.7 % | ||
| CVE-2025-13878 | 9.18.40 – 9.18.43 ; 9.20.13 – 9.20.17 ; 9.21.12 – 9.21.16 ; … | Malformed BRID/HHIT records can cause named to terminate unexpectedly | HIGH 7.5 | 9.4 % | ||
| CVE-2025-40780 | 9.16.0 – 9.16.50 ; 9.18.0 – 9.18.39 ; 9.20.0 – 9.20.13 ; … | Cache poisoning due to weak PRNG | HIGH 8.6 | 0.5 % | ||
| CVE-2025-40778 | 9.11.0 – 9.16.50 ; 9.18.0 – 9.18.39 ; 9.20.0 – 9.20.13 ; … | Cache poisoning attacks with unsolicited RRs | HIGH 8.6 | 0.7 % | ||
| CVE-2025-8677 | 9.18.0 – 9.18.39 ; 9.20.0 – 9.20.13 ; 9.21.0 – 9.21.12 ; … | Resource exhaustion via malformed DNSKEY handling | HIGH 7.5 | 11 % | ||
| CVE-2025-40777 | 9.20.0 – 9.20.10 ; 9.21.0 – 9.21.9 ; 9.20.9-S1 – 9.20.10-S1 | A possible assertion failure when 'stale-answer-client-timeout' is set to '0' | HIGH 7.5 | 1.0 % | ||
| CVE-2025-40776 | 9.11.3-S1 – 9.16.50-S1 ; 9.18.11-S1 – 9.18.37-S1 ; 9.20.9-S1 – 9.20.10-S1 | Birthday Attack against Resolvers supporting ECS | HIGH 8.6 | 0.2 % | ||
| CVE-2025-40775 | 9.20.0 – 9.20.8 ; 9.21.0 – 9.21.7 | DNS message with invalid TSIG causes an assertion failure | HIGH 7.5 | 15 % | ||
| CVE-2024-12705 | 9.18.0 – 9.18.32 ; 9.20.0 – 9.20.4 ; 9.21.0 – 9.21.3 ; … | DNS-over-HTTPS implementation suffers from multiple issues under heavy query load | HIGH 7.5 | 18 % | ||
| CVE-2024-11187 | 9.11.0 – 9.11.37 ; 9.16.0 – 9.16.50 ; 9.18.0 – 9.18.32 ; … | Many records in the additional section cause CPU exhaustion | HIGH 7.5 | 16 % | ||
| CVE-2024-4076 | 9.16.13 – 9.16.50 ; 9.18.0 – 9.18.27 ; 9.19.0 – 9.19.24 ; … | Assertion failure when serving both stale cache data and authoritative zone content | HIGH 7.5 | 2.1 % | ||
| CVE-2024-1975 | 9.0.0 – 9.11.37 ; 9.16.0 – 9.16.50 ; 9.18.0 – 9.18.27 ; … | SIG(0) can be used to exhaust CPU resources | HIGH 7.5 | 2.1 % | ||
| CVE-2024-1737 | 9.11.0 – 9.11.37 ; 9.16.0 – 9.16.50 ; 9.18.0 – 9.18.27 ; … | BIND's database will be slow if a very large number of RRs exist at the same name | HIGH 7.5 | 2.1 % | ||
| CVE-2024-0760 | 9.18.1 – 9.18.27 ; 9.19.0 – 9.19.24 ; 9.18.11-S1 – 9.18.27-S1 | A flood of DNS messages over TCP may make the server unstable | HIGH 7.5 | 4.7 % | ||
| CVE-2023-6516 | 9.16.0 – 9.16.45 ; 9.16.8-S1 – 9.16.45-S1 | Specific recursive query patterns may lead to an out-of-memory condition | HIGH 7.5 | 1.1 % | ||
| CVE-2023-5680 | 9.11.3-S1 – 9.11.37-S1 ; 9.16.8-S1 – 9.16.45-S1 ; 9.18.11-S1 – 9.18.21-S1 | Cleaning an ECS-enabled cache may cause excessive CPU load | MEDIUM 5.3 | 0.6 % | ||
| CVE-2023-5679 | 9.16.12 – 9.16.45 ; 9.18.0 – 9.18.21 ; 9.19.0 – 9.19.19 ; … | Enabling both DNS64 and serve-stale may cause an assertion failure during recursive resolution | HIGH 7.5 | 1.3 % | ||
| CVE-2023-5517 | 9.12.0 – 9.16.45 ; 9.18.0 – 9.18.21 ; 9.19.0 – 9.19.19 ; … | Querying RFC 1918 reverse zones may cause an assertion failure when "nxdomain-redirect" is enabled | HIGH 7.5 | 1.3 % | ||
| CVE-2023-4408 | 9.0.0 – 9.16.45 ; 9.18.0 – 9.18.21 ; 9.19.0 – 9.19.19 ; … | Parsing large DNS messages may cause excessive CPU load | HIGH 7.5 | 1.4 % | ||
| CVE-2023-4236 | 9.18.0 – 9.18.18 ; 9.18.11-S1 – 9.18.18-S1 | named may terminate unexpectedly under high DNS-over-TLS query load | HIGH 7.5 | 2.2 % | ||
| CVE-2023-3341 | 9.2.0 – 9.16.43 ; 9.18.0 – 9.18.18 ; 9.19.0 – 9.19.16 ; … | A stack exhaustion flaw in control channel code may cause named to terminate unexpectedly | HIGH 7.5 | 3.0 % | ||
| CVE-2023-2911 | 9.16.33 – 9.16.41 ; 9.18.7 – 9.18.15 ; 9.16.33-S1 – 9.16.41-S1 ; … | Exceeding the recursive-clients quota may cause named to terminate unexpectedly when stale-answer-client-timeout is set to 0 | HIGH 7.5 | 2.5 % | ||
| CVE-2023-2829 | 9.16.8-S1 – 9.16.41-S1 ; 9.18.11-S1 – 9.18.15-S1 | Malformed NSEC records can cause named to terminate unexpectedly when synth-from-dnssec is enabled | HIGH 7.5 | 0.9 % | ||
| CVE-2023-2828 | 9.11.0 – 9.16.41 ; 9.18.0 – 9.18.15 ; 9.19.0 – 9.19.13 ; … | named's configured cache size limit can be significantly exceeded | HIGH 7.5 | 3.7 % | ||
| CVE-2022-3924 | 9.16.12 – 9.16.36 ; 9.18.0 – 9.18.10 ; 9.19.0 – 9.19.8 ; … | named configured to answer from stale cache may terminate unexpectedly at recursive-clients soft quota | HIGH 7.5 | 16 % | ||
| CVE-2022-3736 | 9.16.12 – 9.16.36 ; 9.18.0 – 9.18.10 ; 9.19.0 – 9.19.8 ; … | named configured to answer from stale cache may terminate unexpectedly while processing RRSIG queries | HIGH 7.5 | 49 % | ||
| CVE-2022-3488 | 9.11.4-S1 – 9.11.37-S1 ; 9.16.8-S1 – 9.16.36-S1 | named may terminate unexpectedly when processing ECS options in repeated responses to iterative queries | HIGH 7.5 | 19 % | ||
| CVE-2022-3094 | 9.16.0 – 9.16.36 ; 9.18.0 – 9.18.10 ; 9.19.0 – 9.19.8 ; … | An UPDATE message flood may cause named to exhaust all available memory | HIGH 7.5 | 13 % | ||
| CVE-2019-6476 | 9.14.0 up to 9.14.6 ; 9.15.0 up to 9.15.4 | An error in QNAME minimization code can cause BIND to exit with an assertion failure | HIGH 7.5 | 2.9 % | ||
| CVE-2019-6475 | 9.14.0 up to 9.14.6 ; 9.15.0 up to 9.15.4 | A flaw in mirror zone validity checking can allow zone data to be spoofed | HIGH 7.5 | 1.3 % | ||
| CVE-2019-6471 | BIND 9.11.0 -> 9.11.7, 9.12.0 -> 9.12.4-P1, 9.14.0 -> 9.14.2. Also all releases of the BIND 9.13 development branch and version 9.15.0 of the BIND 9.15 development branch and BIND Supported Preview Edition versions 9.11.3-S1 -> 9.11.7-S1. | A race condition when discarding malformed packets can cause BIND to exit with an assertion failure | MEDIUM 5.9 | 3.3 % | ||
| CVE-2019-6467 | BIND 9.12.0-> 9.12.4, 9.14.0. Also affects all releases in the 9.13 development branch. | An error in the nxdomain redirect feature can cause BIND to exit with an INSIST assertion failure in query.c | HIGH 7.5 | 5.5 % | ||
| CVE-2019-6465 | BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.5-P2, 9.12.0 -> 9.12.3-P2, and versions 9.9.3-S1 -> 9.11.5-S3 of BIND 9 Supported Preview Edition. Versions 9.13.0 -> 9.13.6 of the 9.13 development branch are also affected. Versions prior to BIND 9.9.0 have not been evaluated for vulnerability to CVE-2019-6465. | Zone transfer controls for writable DLZ zones were not effective | MEDIUM 5.3 | 4.0 % | ||
| CVE-2018-5745 | BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.5-P1, 9.12.0 -> 9.12.3-P1, and versions 9.9.3-S1 -> 9.11.5-S3 of BIND 9 Supported Preview Edition. Versions 9.13.0 -> 9.13.6 of the 9.13 development branch are also affected. Versions prior to BIND 9.9.0 have not been evaluated for vulnerability to CVE-2018-5745. | An assertion failure can occur if a trust anchor rolls over to an unsupported key algorithm when using managed-keys | MEDIUM 4.9 | 2.3 % | ||
| CVE-2018-5744 | BIND 9.10.7 -> 9.10.8-P1, 9.11.3 -> 9.11.5-P1, 9.12.0 -> 9.12.3-P1, and versions 9.10.7-S1 -> 9.11.5-S3 of BIND 9 Supported Preview Edition. Versions 9.13.0 -> 9.13.6 of the 9.13 development branch are also affected. | A specially crafted packet can cause named to leak memory | HIGH 7.5 | 3.4 % | ||
| CVE-2018-5743 | BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.6, 9.12.0 -> 9.12.4, 9.14.0. BIND 9 Supported Preview Edition versions 9.9.3-S1 -> 9.11.5-S3, and 9.11.5-S5. Versions 9.13.0 -> 9.13.7 of the 9.13 development branch are also affected. Versions prior to BIND 9.9.0 have not been evaluated for vulnerability to CVE-2018-5743. | Limiting simultaneous TCP clients was ineffective | HIGH 7.5 | 6.5 % | ||
| CVE-2018-5741 | BIND 9 Versions prior to BIND 9.11.5 and BIND 9.12.3 | Update policies krb5-subdomain and ms-subdomain do not enforce controls promised in their documentation | MEDIUM 6.5 | 3.5 % | ||
| CVE-2018-5740 | BIND 9 9.7.0->9.8.8, 9.9.0->9.9.13, 9.10.0->9.10.8, 9.11.0->9.11.4, 9.12.0->9.12.2, 9.13.0->9.13.2 | A flaw in the "deny-answer-aliases" feature can cause an assertion failure in named | HIGH 7.5 | 60 % | ||
| CVE-2018-5738 | 9.9.12, 9.10.7, 9.11.3, 9.12.0->9.12.1-P2, the development release 9.13.0, and also releases 9.9.12-S1, 9.10.7-S1, 9.11.3-S1, and 9.11.3-S2 from BIND 9 Supported Preview Edition. | Some versions of BIND can improperly permit recursive query service to unauthorized clients | HIGH 7.5 | 11 % | ||
| CVE-2018-5737 | 9.12.0 and 9.12.1 | BIND 9.12's serve-stale implementation can cause an assertion failure in rbtdb.c or other undesirable behavior, even if serve-stale is no… | HIGH 7.5 | 10 % | ||
| CVE-2018-5734 | 9.10.5-S1 to 9.10.5-S4, 9.10.6-S1, 9.10.6-S2 | A malformed request can trigger an assertion failure in badcache.c | HIGH 7.5 | 6.3 % | ||
| CVE-2017-3145 | 9.0.0 to 9.8.x, 9.9.0 to 9.9.11, 9.10.0 to 9.10.6, 9.11.0 to 9.11.2, 9.9.3-S1 to 9.9.11-S1, 9.10.5-S1 to 9.10.6-S1, 9.12.0a1 to 9.12.0rc1 | Improper fetch cleanup sequencing in the resolver can cause named to crash | HIGH 7.5 | 28 % | ||
| CVE-2017-3143 | 9.4.0->9.8.8, 9.9.0->9.9.10-P1, 9.10.0->9.10.5-P1, 9.11.0->9.11.1-P1, 9.9.3-S1->9.9.10-S2, 9.10.5-S1->9.10.5-S2 | An error in TSIG authentication can permit unauthorized dynamic updates | HIGH 7.5 | 18 % | ||
| CVE-2017-3142 | 9.4.0->9.8.8, 9.9.0->9.9.10-P1, 9.10.0->9.10.5-P1, 9.11.0->9.11.1-P1, 9.9.3-S1->9.9.10-S2, 9.10.5-S1->9.10.5-S2 | An error in TSIG authentication can permit unauthorized zone transfers | MEDIUM 5.3 | 5.4 % | ||
| CVE-2017-3141 | 9.2.6-P2->9.2.9, 9.3.2-P1->9.3.6, 9.4.0->9.8.8, 9.9.0->9.9.10, 9.10.0->9.10.5, 9.11.0->9.11.1, 9.9.3-S1->9.9.10-S1, 9.10.5-S1 | Windows service and uninstall paths are not quoted when BIND is installed | HIGH 7.8 | 1.4 % | ||
| CVE-2017-3140 | 9.9.10, 9.10.5, 9.11.0->9.11.1, 9.9.10-S1, 9.10.5-S1 | An error processing RPZ rules can cause named to loop endlessly after handling a query | MEDIUM 5.9 | 12 % | ||
| CVE-2017-3138 | 9.9.9->9.9.9-P7, 9.9.10b1->9.9.10rc2, 9.10.4->9.10.4-P7, 9.10.5b1->9.10.5rc2, 9.11.0->9.11.0-P4, 9.11.1b1->9.11.1rc2, 9.9.9-S1->9.9.9-S9 | named exits with a REQUIRE assertion failure if it receives a null command string on its control channel | MEDIUM 6.5 | 5.5 % | ||
| CVE-2017-3137 | 9.9.9-P6, 9.9.10b1->9.9.10rc1, 9.10.4-P6, 9.10.5b1->9.10.5rc1, 9.11.0-P3, 9.11.1b1->9.11.1rc1, and 9.9.9-S8 | A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME | HIGH 7.5 | 9.0 % | ||
| CVE-2017-3136 | 9.8.0 -> 9.8.8-P1, 9.9.0 -> 9.9.9-P6, 9.9.10b1->9.9.10rc1, 9.10.0 -> 9.10.4-P6, 9.10.5b1->9.10.5rc1, 9.11.0 -> 9.11.0-P3, 9.11.1b1->9.11.1rc1, 9.9.3-S1 -> 9.9.9-S8 | An error handling synthesized records could cause an assertion failure when using DNS64 with "break-dnssec yes;" | MEDIUM 5.9 | 11 % | ||
| CVE-2017-3135 | BIND 9 9.8.8, 9.9.3-S1 -> 9.9.9-S7, 9.9.3 -> 9.9.9-P5, 9.9.10b1, 9.10.0 -> 9.10.4-P5, 9.10.5b1, 9.11.0 -> 9.11.0-P2, 9.11.1b1 | Combination of DNS64 and RPZ Can Lead to Crash | HIGH 7.5 | 17 % | ||
| CVE-2016-9778 | BIND 9 9.9.8-S1 -> 9.9.8-S3, 9.9.9-S1 -> 9.9.9-S6, 9.11.0-9.11.0-P1 | An error handling certain queries using the nxdomain-redirect feature could cause a REQUIRE assertion failure in db.c | HIGH 7.5 | 6.8 % |