Описание
ELSA-2024-11232: unbound:1.16.2 security update (MODERATE)
[1.16.2-8.1]
- Fix unbounded name compression could lead to Denial of Service (CVE-2024-8508)
[1.16.2-8]
- Ensure group access correction reaches also updated configs (CVE-2024-1488)
[1.16.2-7]
- Ensure only unbound group can change configuration (CVE-2024-1488)
[1.16.2-6]
- Fix KeyTrap - Extreme CPU consumption in DNSSEC validator CVE-2023-50387
- Fix Preparing an NSEC3 closest encloser proof can exhaust CPU resources CVE-2023-50868
- Resolves: RHEL-25671
- Resolves: RHEL-25643
Обновленные пакеты
Oracle Linux 9
Oracle Linux aarch64
python3-unbound
1.16.2-8.el9_5.1
unbound
1.16.2-8.el9_5.1
unbound-devel
1.16.2-8.el9_5.1
unbound-libs
1.16.2-8.el9_5.1
Oracle Linux x86_64
python3-unbound
1.16.2-8.el9_5.1
unbound
1.16.2-8.el9_5.1
unbound-devel
1.16.2-8.el9_5.1
unbound-libs
1.16.2-8.el9_5.1
Связанные CVE
Связанные уязвимости
NLnet Labs Unbound up to and including version 1.21.0 contains a vulnerability when handling replies with very large RRsets that it needs to perform name compression for. Malicious upstreams responses with very large RRsets can cause Unbound to spend a considerable time applying name compression to downstream replies. This can lead to degraded performance and eventually denial of service in well orchestrated attacks. The vulnerability can be exploited by a malicious actor querying Unbound for the specially crafted contents of a malicious zone with very large RRsets. Before Unbound replies to the query it will try to apply name compression which was an unbounded operation that could lock the CPU until the whole packet was complete. Unbound version 1.21.1 introduces a hard limit on the number of name compression calculations it is willing to do per packet. Packets that need more compression will result in semi-compressed packets or truncated packets, even on TCP for huge messages, to ...
NLnet Labs Unbound up to and including version 1.21.0 contains a vulnerability when handling replies with very large RRsets that it needs to perform name compression for. Malicious upstreams responses with very large RRsets can cause Unbound to spend a considerable time applying name compression to downstream replies. This can lead to degraded performance and eventually denial of service in well orchestrated attacks. The vulnerability can be exploited by a malicious actor querying Unbound for the specially crafted contents of a malicious zone with very large RRsets. Before Unbound replies to the query it will try to apply name compression which was an unbounded operation that could lock the CPU until the whole packet was complete. Unbound version 1.21.1 introduces a hard limit on the number of name compression calculations it is willing to do per packet. Packets that need more compression will result in semi-compressed packets or truncated packets, even on TCP for huge messages, to ...
NLnet Labs Unbound up to and including version 1.21.0 contains a vulnerability when handling replies with very large RRsets that it needs to perform name compression for. Malicious upstreams responses with very large RRsets can cause Unbound to spend a considerable time applying name compression to downstream replies. This can lead to degraded performance and eventually denial of service in well orchestrated attacks. The vulnerability can be exploited by a malicious actor querying Unbound for the specially crafted contents of a malicious zone with very large RRsets. Before Unbound replies to the query it will try to apply name compression which was an unbounded operation that could lock the CPU until the whole packet was complete. Unbound version 1.21.1 introduces a hard limit on the number of name compression calculations it is willing to do per packet. Packets that need more compression will result in semi-compressed packets or truncated packets, even on TCP for huge messages, to avo
NLnet Labs Unbound up to and including version 1.21.0 contains a vulne ...