#20238 closed enhancement (fixed)
unbound-1.21.0
Reported by: | Bruce Dubbs | Owned by: | Bruce Dubbs |
---|---|---|---|
Priority: | elevated | Milestone: | 12.2 |
Component: | BOOK | Version: | git |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
New minor version.
Change History (5)
comment:1 by , 8 months ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 8 months ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Fixed at commits
b0ff7d03f3 Update to gnutls-3.8.7.1. 61c7e618c6 Update to btrfs-progs-6.10.1. 5ac862b215 Update to unbound-1.21.0.
comment:4 by , 8 months ago
Priority: | normal → elevated |
---|
This version has multiple security fixes regarding CacheFlush.
https://lists.nlnetlabs.nl/pipermail/unbound-users/2024-August/008377.html announces the release of version 1.21.0 of this DNS server, including: > This release has a fix for the CAMP and CacheFlush issues. They have a > low severity for Unbound, since it does not affect Unbound so much. > > The Compositional Amplification (CAMP) type of attacks can lead to DoS > attacks against DNS servers. In Unbound legitimate client requests to > the resolvers under typical workload are not directly affected by CAMP > attacks. However we introduce a global quota for 128 outgoing packets > per query (and it's subqueries) that is never reset to prevent the > combination of CAMP with other amplification attacks in the future. We > would like to thank Huayi Duan, Marco Bearzi, Jodok Vieli, and Cagin > Tanir from NetSec group, ETH Zurich for discovering and notifying us > about the issue. This appears to refer to: https://www.usenix.org/conference/usenixsecurity24/presentation/duan > The CacheFlush type of attacks (NSCacheFlush, CNAMECacheFlush) try to > evict cached data by utilizing rogue zones and a steady rogue stream to > a resolver. Based on the zone, the stream, the configured cache size > and the legitimate traffic, Unbound could experience a degradation of > service if a useful entry is evicted and Unbound needs to resolve again. > As a mitigation to the NSCacheFlush attack Unbound is setting a limit > of 20 RRs in an NS RRset. We would like to thank Yehuda Afek, Anat > Bremler-Barr, Shoham Danino and Yuval Shavitt (Tel-Aviv University and > Reichman University) for discovering and notifying us about the issue. This appears to refer to: https://www.usenix.org/conference/usenixsecurity24/presentation/afek > - Fix #1071: [FR] Clear both in-memory and cachedb module cache with > `unbound-control flush*` commands. This appears to have been assigned CVE-2024-43167: https://www.cve.org/CVERecord?id=CVE-2024-43167
These papers are really interesting! https://www.usenix.org/system/files/usenixsecurity24-duan.pdf and https://www.usenix.org/system/files/usenixsecurity24-afek.pdf
Note:
See TracTickets
for help on using tickets.