RHSA-2024:1780: Important: unbound security and bug fix update

The unbound packages provide a validating, recursive, and caching DNS or DNSSECresolver.Security Fix(es): A vulnerability was found in Unbound due to incorrect default permissions, allowing any process outside the unbound group to modify the unbound runtimeconfiguration. The default combination of the "control-use-cert: no" option witheither explicit or implicit use of an IP address in the "control-interface"option could allow improper access. If a process can connect over localhost toport 8953, it can alter the configuration of unbound.service. This flaw allowsan unprivileged local process to manipulate a running instance, potentiallyaltering forwarders, allowing them to track all queries forwarded by the localresolver, and, in some cases, disrupting resolving altogether.To mitigate the vulnerability, a new file"/etc/unbound/conf.d/remote-control.conf" has been added and included in themain unbound configuration file, "unbound.conf". The file contains twodirectives that should limit access to unbound.conf:control-interface: "/run/unbound/control" control-use-cert: "yes"For details about these directives, run "man unbound.conf".Updating to the version of unbound provided by this advisory should, in mostcases, address the vulnerability. To verify that your configuration is notvulnerable, use the "unbound-control status | grep control" command. If theoutput contains "control(ssl)" or "control(namedpipe)", your configuration isnot vulnerable. If the command output returns only "control", the configurationis vulnerable because it does not enforce access only to the unbound groupmembers. To fix your configuration, add the line "include:/etc/unbound/conf.d/remote-control.conf" to the end of the file"/etc/unbound/unbound.conf". If you use a custom"/etc/unbound/conf.d/remote-control.conf" file, add the new directives to thisfile. (CVE-2024-1488)For more details about the security issue(s), including the impact, a CVSSscore, acknowledgments, and other related information, refer to the CVE page(s)listed in the References section.

— Red Hat