Login
Newsletter
Werbung

Sicherheit: Mehrere Probleme in unbound
Aktuelle Meldungen Distributionen
Name: Mehrere Probleme in unbound
ID: RHSA-2024:1801
Distribution: Red Hat
Plattformen: Red Hat Enterprise Linux AppStream EUS (v.9.0)
Datum: Mo, 15. April 2024, 22:20
Referenzen: https://bugzilla.redhat.com/show_bug.cgi?id=2263917
https://bugzilla.redhat.com/show_bug.cgi?id=2263914
https://access.redhat.com/security/cve/CVE-2023-50868
https://access.redhat.com/security/cve/CVE-2024-1488
https://access.redhat.com/security/cve/CVE-2023-50387
https://bugzilla.redhat.com/show_bug.cgi?id=2264183
https://access.redhat.com/errata/RHSA-2024:1801
Applikationen: Unbound

Originalnachricht

An update for unbound is now available for Red Hat Enterprise Linux 9.0
Extended Update Support.

Red Hat Product Security has rated this update as having a security impact of
Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

The unbound packages provide a validating, recursive, and caching DNS or DNSSEC
resolver.

Security Fix(es):

* bind9: KeyTrap - Extreme CPU consumption in DNSSEC validator (CVE-2023-50387)

* bind9: Preparing an NSEC3 closest encloser proof can exhaust CPU resources
(CVE-2023-50868)

* A vulnerability was found in Unbound due to incorrect default permissions,
allowing any process outside the unbound group to modify the unbound runtime
configuration. The default combination of the "control-use-cert: no"
option with
either explicit or implicit use of an IP address in the
"control-interface"
option could allow improper access. If a process can connect over localhost to
port 8953, it can alter the configuration of unbound.service. This flaw allows
an unprivileged local process to manipulate a running instance, potentially
altering forwarders, allowing them to track all queries forwarded by the local
resolver, 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 the
main unbound configuration file, "unbound.conf". The file contains two
directives 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 most
cases, address the vulnerability. To verify that your configuration is not
vulnerable, use the "unbound-control status | grep control" command. If
the
output contains "control(ssl)" or "control(namedpipe)", your
configuration is
not vulnerable. If the command output returns only "control", the
configuration
is vulnerable because it does not enforce access only to the unbound group
members. 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 this
file. (CVE-2024-1488)

For more details about the security issue(s), including the impact, a CVSS
score, acknowledgments, and other related information, refer to the CVE page(s)
listed in the References section.

This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Red Hat Inc. and provide a link to the original.

CVE-2023-50387: Uncontrolled Resource Consumption (CWE-400)
CVE-2023-50868: Uncontrolled Resource Consumption (CWE-400)
CVE-2024-1488: External Control of System or Configuration Setting (CWE-15)
Pro-Linux
Pro-Linux @Facebook
Neue Nachrichten
Werbung