trivy-0.58.2-1.1 on GA media SUSE Patch security@suse.de SUSE Security Team openSUSE-SU-2025:14713-1 Final 1 1 2025-01-29T00:00:00Z current 2025-01-29T00:00:00Z 2025-01-29T00:00:00Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z trivy-0.58.2-1.1 on GA media These are all security issues fixed in the trivy-0.58.2-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-2025-14713 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/JZAWXH6WKGE2WACLTZWYMHTDCJMU3X6R/ E-Mail link for openSUSE-SU-2025:14713-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://www.suse.com/security/cve/CVE-2024-3817/ SUSE CVE CVE-2024-3817 page https://www.suse.com/security/cve/CVE-2024-45337/ SUSE CVE CVE-2024-45337 page https://www.suse.com/security/cve/CVE-2024-45338/ SUSE CVE CVE-2024-45338 page https://www.suse.com/security/cve/CVE-2025-21613/ SUSE CVE CVE-2025-21613 page openSUSE Tumbleweed trivy-0.58.2-1.1 trivy-0.58.2-1.1 as a component of openSUSE Tumbleweed HashiCorp's go-getter library is vulnerable to argument injection when executing Git to discover remote branches. This vulnerability does not affect the go-getter/v2 branch and package. CVE-2024-3817 openSUSE Tumbleweed:trivy-0.58.2-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/JZAWXH6WKGE2WACLTZWYMHTDCJMU3X6R/ https://www.suse.com/security/cve/CVE-2024-3817.html CVE-2024-3817 https://bugzilla.suse.com/1226999 SUSE Bug 1226999 Applications and libraries which misuse connection.serverAuthenticate (via callback field ServerConfig.PublicKeyCallback) may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key. Since this API is widely misused, as a partial mitigation golang.org/x/cry...@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth. Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance. CVE-2024-45337 openSUSE Tumbleweed:trivy-0.58.2-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/JZAWXH6WKGE2WACLTZWYMHTDCJMU3X6R/ https://www.suse.com/security/cve/CVE-2024-45337.html CVE-2024-45337 https://bugzilla.suse.com/1234482 SUSE Bug 1234482 An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service. CVE-2024-45338 openSUSE Tumbleweed:trivy-0.58.2-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/JZAWXH6WKGE2WACLTZWYMHTDCJMU3X6R/ https://www.suse.com/security/cve/CVE-2024-45338.html CVE-2024-45338 https://bugzilla.suse.com/1234794 SUSE Bug 1234794 go-git is a highly extensible git implementation library written in pure Go. An argument injection vulnerability was discovered in go-git versions prior to v5.13. Successful exploitation of this vulnerability could allow an attacker to set arbitrary values to git-upload-pack flags. This only happens when the file transport protocol is being used, as that is the only protocol that shells out to git binaries. This vulnerability is fixed in 5.13.0. CVE-2025-21613 openSUSE Tumbleweed:trivy-0.58.2-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/JZAWXH6WKGE2WACLTZWYMHTDCJMU3X6R/ https://www.suse.com/security/cve/CVE-2025-21613.html CVE-2025-21613 https://bugzilla.suse.com/1235572 SUSE Bug 1235572