Описание
Security update for rekor
This update for rekor fixes the following issues:
Security fixes:
- CVE-2025-58058: Fixed github.com/ulikunitz/xz leaks memory (bsc#1248910)
- CVE-2025-29923: Fixed potential out of order responses when
CLIENT SETINFOtimes out during connection establishment (bsc#1241153)
Other fixes:
- Update to version 1.4.3
- Update to version 1.4.2
- Update to version 1.4.1 (jsc#SLE-23476)
Список пакетов
SUSE Linux Enterprise Module for Basesystem 15 SP7
openSUSE Leap 15.6
Ссылки
- Link for SUSE-SU-2026:0383-1
- E-Mail link for SUSE-SU-2026:0383-1
- SUSE Security Ratings
- SUSE Bug 1241153
- SUSE Bug 1248910
- SUSE CVE CVE-2025-29923 page
- SUSE CVE CVE-2025-58058 page
Описание
go-redis is the official Redis client library for the Go programming language. Prior to 9.5.5, 9.6.3, and 9.7.3, go-redis potentially responds out of order when `CLIENT SETINFO` times out during connection establishment. This can happen when the client is configured to transmit its identity, there are network connectivity issues, or the client was configured with aggressive timeouts. The problem occurs for multiple use cases. For sticky connections, you receive persistent out-of-order responses for the lifetime of the connection. All commands in the pipeline receive incorrect responses. When used with the default ConnPool once a connection is returned after use with ConnPool#Put the read buffer will be checked and the connection will be marked as bad due to the unread data. This means that at most one out-of-order response before the connection is discarded. This issue is fixed in 9.5.5, 9.6.3, and 9.7.3. You can prevent the vulnerability by setting the flag DisableIndentity to true when constructing the client instance.
Затронутые продукты
Ссылки
- CVE-2025-29923
- SUSE Bug 1241152
Описание
xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn't include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14.
Затронутые продукты
Ссылки
- CVE-2025-58058
- SUSE Bug 1248889