trivy-0.59.1-1.1 on GA media SUSE Patch security@suse.de SUSE Security Team openSUSE-SU-2025:14840-1 Final 1 1 2025-02-26T00:00:00Z current 2025-02-26T00:00:00Z 2025-02-26T00:00:00Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z trivy-0.59.1-1.1 on GA media These are all security issues fixed in the trivy-0.59.1-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-14840 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-51744/ SUSE CVE CVE-2024-51744 page https://www.suse.com/security/cve/CVE-2025-27144/ SUSE CVE CVE-2025-27144 page openSUSE Tumbleweed trivy-0.59.1-1.1 trivy-0.59.1-1.1 as a component of openSUSE Tumbleweed golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above. CVE-2024-51744 openSUSE Tumbleweed:trivy-0.59.1-1.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-51744.html CVE-2024-51744 https://bugzilla.suse.com/1232936 SUSE Bug 1232936 Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. In versions on the 4.x branch prior to version 4.0.5, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code used strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of `.` characters. An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service. Version 4.0.5 fixes this issue. As a workaround, applications could pre-validate that payloads passed to Go JOSE do not contain an excessive number of `.` characters. CVE-2025-27144 openSUSE Tumbleweed:trivy-0.59.1-1.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-2025-27144.html CVE-2025-27144 https://bugzilla.suse.com/1237608 SUSE Bug 1237608 https://bugzilla.suse.com/1237609 SUSE Bug 1237609