| CVE-2023-6516 |
To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to clean up the…
|
7.5
Élevée
|
13 févr. 2024 |
| CVE-2023-5680 |
If a resolver cache has a very large number of ECS records stored for the same name, the process of cleaning the cache…
|
5.3
Moyenne
|
13 févr. 2024 |
| CVE-2023-5679 |
A bad interaction between DNS64 and serve-stale may cause `named` to crash with an assertion failure during recursive…
|
7.5
Élevée
|
13 févr. 2024 |
| CVE-2023-5517 |
A flaw in query-handling code can cause `named` to exit prematurely with an assertion failure when: -…
|
7.5
Élevée
|
13 févr. 2024 |
| CVE-2023-4408 |
The DNS message parsing code in `named` includes a section whose computational complexity is overly high
|
7.5
Élevée
|
13 févr. 2024 |
| CVE-2023-4236 |
A flaw in the networking code handling DNS-over-TLS queries may cause `named` to terminate unexpectedly due to an…
|
7.5
Élevée
|
20 sept. 2023 |
| CVE-2023-3341 |
The code that processes control channel messages sent to `named` calls certain functions recursively during packet…
|
7.5
Élevée
|
20 sept. 2023 |
| CVE-2023-2911 |
If the `recursive-clients` quota is reached on a BIND 9 resolver configured with both `stale-answer-enable yes;` and…
|
7.5
Élevée
|
21 juin 2023 |
| CVE-2023-2829 |
A `named` instance configured to run as a DNSSEC-validating recursive resolver with the Aggressive Use of…
|
7.5
Élevée
|
21 juin 2023 |
| CVE-2023-2828 |
Every `named` instance configured to run as a recursive resolver maintains a cache database holding the responses to the…
|
7.5
Élevée
|
21 juin 2023 |
| CVE-2022-3924 |
This issue can affect BIND 9 resolvers with `stale-answer-enable yes;` that also make use of the option…
|
7.5
Élevée
|
25 janv. 2023 |
| CVE-2022-3736 |
BIND 9 resolver can crash when stale cache and stale answers are enabled, option `stale-answer-client-timeout` is set to…
|
7.5
Élevée
|
25 janv. 2023 |
| CVE-2022-3488 |
Processing of repeated responses to the same query, where both responses contain ECS pseudo-options, but where the first…
|
7.5
Élevée
|
25 janv. 2023 |
| CVE-2022-3094 |
Sending a flood of dynamic DNS updates may cause `named` to allocate large amounts of memory
|
7.5
Élevée
|
25 janv. 2023 |
| CVE-2019-6476 |
A defect in code added to support QNAME minimization can cause named to exit with an assertion failure if a forwarder…
|
5.9
Moyenne
|
17 oct. 2019 |
| CVE-2019-6475 |
Mirror zones are a BIND feature allowing recursive servers to pre-cache zone data provided by other servers
|
5.9
Moyenne
|
17 oct. 2019 |
| CVE-2019-6471 |
A race condition which may occur when discarding malformed packets can result in BIND exiting due to a REQUIRE assertion…
|
5.9
Moyenne
|
9 oct. 2019 |
| CVE-2019-6467 |
A programming error in the nxdomain-redirect feature can cause an assertion failure in query.c if the alternate…
|
5.9
Moyenne
|
9 oct. 2019 |
| CVE-2019-6465 |
Controls for zone transfers may not be properly applied to Dynamically Loadable Zones (DLZs) if the zones are writable…
|
5.3
Moyenne
|
9 oct. 2019 |
| CVE-2018-5745 |
"managed-keys" is a feature which allows a BIND resolver to automatically maintain the keys used by trust anchors…
|
4.9
Moyenne
|
9 oct. 2019 |
| CVE-2018-5744 |
A failure to free memory can occur when processing messages having a specific combination of EDNS options
|
7.5
Élevée
|
9 oct. 2019 |
| CVE-2018-5743 |
By design, BIND is intended to limit the number of TCP clients that can be connected at any given time
|
7.5
Élevée
|
9 oct. 2019 |
| CVE-2018-5740 |
"deny-answer-aliases" is a little-used feature intended to help recursive server operators protect end users against DNS…
|
7.5
Élevée
|
16 janv. 2019 |
| CVE-2018-5738 |
Change #4777 (introduced in October 2017) introduced an unforeseen issue in releases which were issued after that…
|
5.3
Moyenne
|
16 janv. 2019 |
| CVE-2018-5737 |
A problem with the implementation of the new serve-stale feature in BIND 9.12 can lead to an assertion failure in…
|
5.9
Moyenne
|
16 janv. 2019 |