Tweak and reword release notes

This commit is contained in:
Michal Nowak
2023-06-09 16:18:38 +02:00
parent 35a43186a6
commit 606af41ced

View File

@@ -15,27 +15,27 @@ Notes for BIND 9.16.42
Security Fixes
~~~~~~~~~~~~~~
- The overmem cleaning process has been improved, to prevent the cache from
significantly exceeding the configured ``max-cache-size`` limit.
- The overmem cleaning process has been improved, to prevent the cache
from significantly exceeding the configured ``max-cache-size`` limit.
(CVE-2023-2828)
ISC would like to thank Shoham Danino from Reichman University, Anat
Bremler-Barr from Tel-Aviv University, Yehuda Afek from Tel-Aviv University,
and Yuval Shavitt from Tel-Aviv University for bringing this vulnerability to
our attention. :gl:`#4055`
Bremler-Barr from Tel-Aviv University, Yehuda Afek from Tel-Aviv
University, and Yuval Shavitt from Tel-Aviv University for bringing
this vulnerability to our attention. :gl:`#4055`
- 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 :iscman:`named` to enter an infinite callback
loop and crash due to stack overflow. This has been fixed. (CVE-2023-2911)
:gl:`#4089`
- 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 :iscman:`named` to enter an
infinite callback loop and crash due to stack overflow. This has been
fixed. (CVE-2023-2911) :gl:`#4089`
Bug Fixes
~~~~~~~~~
- It could happen that after the ``stale-answer-client-timeout`` duration,
a delegation from cache was returned to the client. This has now been fixed.
:gl:`#3950`
- 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`
Known Issues
~~~~~~~~~~~~