mirror of
https://git.openwrt.org/feed/packages.git
synced 2024-06-15 11:53:59 +02:00
33f24874df
Imported patches included in debian and other package.
* 200-Fix-NULL-pointer-crashes-from-175.patch
CVE-2021-3502
A flaw was found in avahi 0.8-5. A reachable assertion is present in avahi_s_host_name_resolver_start function allowing a local attacker to crash the avahi service by requesting hostname resolutions through the avahi socket or dbus methods for invalid hostnames. The highest threat from this vulnerability is to the service availability.
* 201-Avoid-infinite-loop-in-avahi-daemon-by-handling-HUP-event.patch
CVE-2021-3468
A flaw was found in avahi in versions 0.6 up to 0.8. The event used to signal the termination of the client connection on the avahi Unix socket is not correctly handled in the client_work function, allowing a local attacker to trigger an infinite loop. The highest threat from this vulnerability is to the availability of the avahi service, which becomes unresponsive after this flaw is triggered.
* 202-avahi_dns_packet_consume_uint32-fix-potential-undefined-b.patch
avahi_dns_packet_consume_uint32 left shifts uint8_t values by 8, 16 and 24 bits to combine them into a 32-bit value. This produces an undefined behavior warning with gcc -fsanitize when fed input values of 128 or 255 however in testing no actual unexpected behavior occurs in practice and the 32-bit uint32_t is always correctly produced as the final value is immediately stored into a uint32_t and the compiler appears to handle this "correctly".
Cast the intermediate values to uint32_t to prevent this warning and ensure the intended result is explicit.
* 203-Do-not-disable-timeout-cleanup-on-watch-cleanup.patch
This was causing timeouts to never be removed from the linked list that tracks them, resulting in both memory and CPU usage to grow larger over time.
* 204-Emit-error-if-requested-service-is-not-found.patch
It currently just crashes instead of replying with error. Check return
value and emit error instead of passing NULL pointer to reply.
* 205-conf-file-line-lengths.patch
Allow avahi-daemon.conf file to have lines longer than 256 characters (new limit 1024).
Signed-off-by: Hirokazu MORIKAWA <morikw2@gmail.com>
(cherry picked from commit 779af4d40c)
37 lines
1.3 KiB
Diff
37 lines
1.3 KiB
Diff
From: Riccardo Schirone <sirmy15@gmail.com>
|
|
Date: Fri, 26 Mar 2021 11:50:24 +0100
|
|
Subject: Avoid infinite-loop in avahi-daemon by handling HUP event in
|
|
client_work
|
|
|
|
If a client fills the input buffer, client_work() disables the
|
|
AVAHI_WATCH_IN event, thus preventing the function from executing the
|
|
`read` syscall the next times it is called. However, if the client then
|
|
terminates the connection, the socket file descriptor receives a HUP
|
|
event, which is not handled, thus the kernel keeps marking the HUP event
|
|
as occurring. While iterating over the file descriptors that triggered
|
|
an event, the client file descriptor will keep having the HUP event and
|
|
the client_work() function is always called with AVAHI_WATCH_HUP but
|
|
without nothing being done, thus entering an infinite loop.
|
|
|
|
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984938
|
|
|
|
(cherry picked from commit 447affe29991ee99c6b9732fc5f2c1048a611d3b)
|
|
---
|
|
avahi-daemon/simple-protocol.c | 5 +++++
|
|
1 file changed, 5 insertions(+)
|
|
|
|
--- a/avahi-daemon/simple-protocol.c
|
|
+++ b/avahi-daemon/simple-protocol.c
|
|
@@ -424,6 +424,11 @@ static void client_work(AvahiWatch *watc
|
|
}
|
|
}
|
|
|
|
+ if (events & AVAHI_WATCH_HUP) {
|
|
+ client_free(c);
|
|
+ return;
|
|
+ }
|
|
+
|
|
c->server->poll_api->watch_update(
|
|
watch,
|
|
(c->outbuf_length > 0 ? AVAHI_WATCH_OUT : 0) |
|