govulncheck-vulndb-0.0.20241220T214820-1.1 on GA media SUSE Patch security@suse.de SUSE Security Team openSUSE-SU-2024:14608-1 Final 1 1 2024-12-22T00:00:00Z current 2024-12-22T00:00:00Z 2024-12-22T00:00:00Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z govulncheck-vulndb-0.0.20241220T214820-1.1 on GA media These are all security issues fixed in the govulncheck-vulndb-0.0.20241220T214820-1.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-14608 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/RKGXQ5KH45FY7WLT7M5JFCJB2ZEAPTJA/ E-Mail link for openSUSE-SU-2024:14608-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://www.suse.com/security/cve/CVE-2024-12678/ SUSE CVE CVE-2024-12678 page https://www.suse.com/security/cve/CVE-2024-25131/ SUSE CVE CVE-2024-25131 page https://www.suse.com/security/cve/CVE-2024-43803/ SUSE CVE CVE-2024-43803 page https://www.suse.com/security/cve/CVE-2024-9779/ SUSE CVE CVE-2024-9779 page openSUSE Tumbleweed govulncheck-vulndb-0.0.20241220T214820-1.1 govulncheck-vulndb-0.0.20241220T214820-1.1 as a component of openSUSE Tumbleweed Nomad Community and Nomad Enterprise ("Nomad") allocations are vulnerable to privilege escalation within a namespace through unredacted workload identity tokens. This vulnerability, identified as CVE-2024-12678, is fixed in Nomad Community Edition 1.9.4 and Nomad Enterprise 1.9.4, 1.8.8, and 1.7.16. CVE-2024-12678 openSUSE Tumbleweed:govulncheck-vulndb-0.0.20241220T214820-1.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/RKGXQ5KH45FY7WLT7M5JFCJB2ZEAPTJA/ https://www.suse.com/security/cve/CVE-2024-12678.html CVE-2024-12678 A flaw was found in the MustGather.managed.openshift.io Custom Defined Resource (CRD) of OpenShift Dedicated. A non-privileged user on the cluster can create a MustGather object with a specially crafted file and set the most privileged service account to run the job. This can allow a standard developer user to escalate their privileges to a cluster administrator and pivot to the AWS environment. CVE-2024-25131 openSUSE Tumbleweed:govulncheck-vulndb-0.0.20241220T214820-1.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/RKGXQ5KH45FY7WLT7M5JFCJB2ZEAPTJA/ https://www.suse.com/security/cve/CVE-2024-25131.html CVE-2024-25131 The Bare Metal Operator (BMO) implements a Kubernetes API for managing bare metal hosts in Metal3. The `BareMetalHost` (BMH) CRD allows the `userData`, `metaData`, and `networkData` for the provisioned host to be specified as links to Kubernetes Secrets. There are fields for both the `Name` and `Namespace` of the Secret, meaning that versions of the baremetal-operator prior to 0.8.0, 0.6.2, and 0.5.2 will read a `Secret` from any namespace. A user with access to create or edit a `BareMetalHost` can thus exfiltrate a `Secret` from another namespace by using it as e.g. the `userData` for provisioning some host (note that this need not be a real host, it could be a VM somewhere). BMO will only read a key with the name `value` (or `userData`, `metaData`, or `networkData`), so that limits the exposure somewhat. `value` is probably a pretty common key though. Secrets used by _other_ `BareMetalHost`s in different namespaces are always vulnerable. It is probably relatively unusual for anyone other than cluster administrators to have RBAC access to create/edit a `BareMetalHost`. This vulnerability is only meaningful, if the cluster has users other than administrators and users' privileges are limited to their respective namespaces. The patch prevents BMO from accepting links to Secrets from other namespaces as BMH input. Any BMH configuration is only read from the same namespace only. The problem is patched in BMO releases v0.7.0, v0.6.2 and v0.5.2 and users should upgrade to those versions. Prior upgrading, duplicate the BMC Secrets to the namespace where the corresponding BMH is. After upgrade, remove the old Secrets. As a workaround, an operator can configure BMO RBAC to be namespace scoped for Secrets, instead of cluster scoped, to prevent BMO from accessing Secrets from other namespaces. CVE-2024-43803 openSUSE Tumbleweed:govulncheck-vulndb-0.0.20241220T214820-1.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/RKGXQ5KH45FY7WLT7M5JFCJB2ZEAPTJA/ https://www.suse.com/security/cve/CVE-2024-43803.html CVE-2024-43803 A flaw was found in Open Cluster Management (OCM) when a user has access to the worker nodes which contain the cluster-manager or klusterlet deployments. The cluster-manager deployment uses a service account with the same name "cluster-manager" which is bound to a ClusterRole also named "cluster-manager", which includes the permission to create Pod resources. If this deployment runs a pod on an attacker-controlled node, the attacker can obtain the cluster-manager's token and steal any service account token by creating and mounting the target service account to control the whole cluster. CVE-2024-9779 openSUSE Tumbleweed:govulncheck-vulndb-0.0.20241220T214820-1.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/RKGXQ5KH45FY7WLT7M5JFCJB2ZEAPTJA/ https://www.suse.com/security/cve/CVE-2024-9779.html CVE-2024-9779