docker-stable-24.0.9_ce-6.1 on GA media SUSE Patch security@suse.de SUSE Security Team openSUSE-SU-2024:14598-1 Final 1 1 2024-12-18T00:00:00Z current 2024-12-18T00:00:00Z 2024-12-18T00:00:00Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z docker-stable-24.0.9_ce-6.1 on GA media These are all security issues fixed in the docker-stable-24.0.9_ce-6.1 package on the GA media of openSUSE Tumbleweed. The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). openSUSE-Tumbleweed-2024-14598 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/security/rating/ SUSE Security Ratings https://www.suse.com/security/cve/CVE-2024-2365/ SUSE CVE CVE-2024-2365 page https://www.suse.com/security/cve/CVE-2024-23650/ SUSE CVE CVE-2024-23650 page https://www.suse.com/security/cve/CVE-2024-29018/ SUSE CVE CVE-2024-29018 page openSUSE Tumbleweed docker-stable-24.0.9_ce-6.1 docker-stable-bash-completion-24.0.9_ce-6.1 docker-stable-buildx-0.19.3-6.1 docker-stable-fish-completion-24.0.9_ce-6.1 docker-stable-rootless-extras-24.0.9_ce-6.1 docker-stable-zsh-completion-24.0.9_ce-6.1 docker-stable-24.0.9_ce-6.1 as a component of openSUSE Tumbleweed docker-stable-bash-completion-24.0.9_ce-6.1 as a component of openSUSE Tumbleweed docker-stable-buildx-0.19.3-6.1 as a component of openSUSE Tumbleweed docker-stable-fish-completion-24.0.9_ce-6.1 as a component of openSUSE Tumbleweed docker-stable-rootless-extras-24.0.9_ce-6.1 as a component of openSUSE Tumbleweed docker-stable-zsh-completion-24.0.9_ce-6.1 as a component of openSUSE Tumbleweed A vulnerability classified as problematic was found in Musicshelf 1.0/1.1 on Android. Affected by this vulnerability is an unknown functionality of the file io\fabric\sdk\android\services\network\PinningTrustManager.java of the component SHA-1 Handler. The manipulation leads to password hash with insufficient computational effort. It is possible to launch the attack on the physical device. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The identifier VDB-256321 was assigned to this vulnerability. CVE-2024-2365 openSUSE Tumbleweed:docker-stable-24.0.9_ce-6.1 openSUSE Tumbleweed:docker-stable-bash-completion-24.0.9_ce-6.1 openSUSE Tumbleweed:docker-stable-buildx-0.19.3-6.1 openSUSE Tumbleweed:docker-stable-fish-completion-24.0.9_ce-6.1 openSUSE Tumbleweed:docker-stable-rootless-extras-24.0.9_ce-6.1 openSUSE Tumbleweed:docker-stable-zsh-completion-24.0.9_ce-6.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/security/cve/CVE-2024-2365.html CVE-2024-2365 BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. A malicious BuildKit client or frontend could craft a request that could lead to BuildKit daemon crashing with a panic. The issue has been fixed in v0.12.5. As a workaround, avoid using BuildKit frontends from untrusted sources. CVE-2024-23650 openSUSE Tumbleweed:docker-stable-24.0.9_ce-6.1 openSUSE Tumbleweed:docker-stable-bash-completion-24.0.9_ce-6.1 openSUSE Tumbleweed:docker-stable-buildx-0.19.3-6.1 openSUSE Tumbleweed:docker-stable-fish-completion-24.0.9_ce-6.1 openSUSE Tumbleweed:docker-stable-rootless-extras-24.0.9_ce-6.1 openSUSE Tumbleweed:docker-stable-zsh-completion-24.0.9_ce-6.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/security/cve/CVE-2024-23650.html CVE-2024-23650 https://bugzilla.suse.com/1219437 SUSE Bug 1219437 Moby is an open source container framework that is a key component of Docker Engine, Docker Desktop, and other distributions of container tooling or runtimes. Moby's networking implementation allows for many networks, each with their own IP address range and gateway, to be defined. This feature is frequently referred to as custom networks, as each network can have a different driver, set of parameters and thus behaviors. When creating a network, the `--internal` flag is used to designate a network as _internal_. The `internal` attribute in a docker-compose.yml file may also be used to mark a network _internal_, and other API clients may specify the `internal` parameter as well. When containers with networking are created, they are assigned unique network interfaces and IP addresses. The host serves as a router for non-internal networks, with a gateway IP that provides SNAT/DNAT to/from container IPs. Containers on an internal network may communicate between each other, but are precluded from communicating with any networks the host has access to (LAN or WAN) as no default route is configured, and firewall rules are set up to drop all outgoing traffic. Communication with the gateway IP address (and thus appropriately configured host services) is possible, and the host may communicate with any container IP directly. In addition to configuring the Linux kernel's various networking features to enable container networking, `dockerd` directly provides some services to container networks. Principal among these is serving as a resolver, enabling service discovery, and resolution of names from an upstream resolver. When a DNS request for a name that does not correspond to a container is received, the request is forwarded to the configured upstream resolver. This request is made from the container's network namespace: the level of access and routing of traffic is the same as if the request was made by the container itself. As a consequence of this design, containers solely attached to an internal network will be unable to resolve names using the upstream resolver, as the container itself is unable to communicate with that nameserver. Only the names of containers also attached to the internal network are able to be resolved. Many systems run a local forwarding DNS resolver. As the host and any containers have separate loopback devices, a consequence of the design described above is that containers are unable to resolve names from the host's configured resolver, as they cannot reach these addresses on the host loopback device. To bridge this gap, and to allow containers to properly resolve names even when a local forwarding resolver is used on a loopback address, `dockerd` detects this scenario and instead forward DNS requests from the host namework namespace. The loopback resolver then forwards the requests to its configured upstream resolvers, as expected. Because `dockerd` forwards DNS requests to the host loopback device, bypassing the container network namespace's normal routing semantics entirely, internal networks can unexpectedly forward DNS requests to an external nameserver. By registering a domain for which they control the authoritative nameservers, an attacker could arrange for a compromised container to exfiltrate data by encoding it in DNS queries that will eventually be answered by their nameservers. Docker Desktop is not affected, as Docker Desktop always runs an internal resolver on a RFC 1918 address. Moby releases 26.0.0, 25.0.4, and 23.0.11 are patched to prevent forwarding any DNS requests from internal networks. As a workaround, run containers intended to be solely attached to internal networks with a custom upstream address, which will force all upstream DNS queries to be resolved from the container's network namespace. CVE-2024-29018 openSUSE Tumbleweed:docker-stable-24.0.9_ce-6.1 openSUSE Tumbleweed:docker-stable-bash-completion-24.0.9_ce-6.1 openSUSE Tumbleweed:docker-stable-buildx-0.19.3-6.1 openSUSE Tumbleweed:docker-stable-fish-completion-24.0.9_ce-6.1 openSUSE Tumbleweed:docker-stable-rootless-extras-24.0.9_ce-6.1 openSUSE Tumbleweed:docker-stable-zsh-completion-24.0.9_ce-6.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/security/cve/CVE-2024-29018.html CVE-2024-29018 https://bugzilla.suse.com/1234089 SUSE Bug 1234089