#18193 closed enhancement (fixed)
bind9 bind 9.18.16
| Reported by: | Bruce Dubbs | Owned by: | Douglas R. Reno |
|---|---|---|---|
| Priority: | elevated | Milestone: | 12.0 |
| Component: | BOOK | Version: | git |
| Severity: | medium | Keywords: | |
| Cc: |
Description
New point version.
Change History (6)
comment:1 by , 3 years ago
| Priority: | normal → elevated |
|---|
comment:2 by , 3 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 3 years ago
Security Fixes
The overmem cleaning process has been improved, to prevent the cache from
significantly exceeding the configured max-cache-size limit. (CVE-2023-2828)
A query that prioritizes stale data over lookup triggers a fetch to refresh the
stale data in cache. If the fetch is aborted for exceeding the recursion quota, it was
possible for named to enter an infinite callback loop and crash due to stack overflow.
This has been fixed. (CVE-2023-2911) [GL #4089]
New Features
The system test suite can now be executed with pytest (along with pytest-xdist for
parallel execution). [GL #3978]
Removed Features
TKEY mode 2 (Diffie-Hellman Exchanged Keying) is now deprecated, and will be
removed in a future release. A warning will be logged when the tkey-dhkey option is
used in named.conf. [GL #3905]
Bug Fixes
BIND could get stuck on reconfiguration when a listen-on statement for HTTP is
removed from the configuration. That has been fixed. [GL #4071]
Previously, it was possible for a delegation from cache to be returned to the
client after the stale-answer-client-timeout duration. This has been fixed. [GL #3950]
BIND could allocate too big buffers when sending data via stream-based DNS
transports, leading to increased memory usage. This has been fixed. [GL #4038]
When the stale-answer-enable option was enabled and the stale-answer-client-timeout
option was enabled and larger than 0, named previously allocated two slots from the
clients-per-query limit for each client and failed to gradually auto-tune its value, as
configured. This has been fixed. [GL #4074]
Known Issues
There are no new known issues with this release. See above for a list of all known
issues affecting this BIND 9 branch.
comment:4 by , 3 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.

Moving to elevated for security fixes