Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

suse-cvrf логотип

openSUSE-SU-2026:20711-1

Опубликовано: 09 мая 2026
Источник: suse-cvrf

Описание

Security update for hauler

This update for hauler fixes the following issues:

Changes in hauler:

  • update to 1.4.3 ( bsc#1262353, CVE-2026-39984, bsc#1262942, CVE-2026-34986):
    • [1.4] Bump go.opentelemetry.io/otel/sdk from 1.40.0 to 1.43.0 in the go_modules group across 1 directory
    • [1.4] Bump github.com/sigstore/timestamp-authority/v2 from 2.0.4 to 2.0.6 in the go_modules group across 1 directory
    • [1.4] Bump google.golang.org/grpc from 1.78.0 to 1.79.3 in the go_modules group across 1 directory
    • fixed versions and dependencies on release/1.4
    • [1.4] removed unnecessary rewrite flag from sync
    • added makefile command for vulnerability checks (backport #577)
    • remove cherrypick bot and add mergify details (backport #581)

Список пакетов

openSUSE Leap 16.0
hauler-1.4.3-bp160.1.1

Ссылки

Описание

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. Prior to 4.1.4 and 3.0.5, decrypting a JSON Web Encryption (JWE) object will panic if the alg field indicates a key wrapping algorithm (one ending in KW, with the exception of A128GCMKW, A192GCMKW, and A256GCMKW) and the encrypted_key field is empty. The panic happens when cipher.KeyUnwrap() in key_wrap.go attempts to allocate a slice with a zero or negative length based on the length of the encrypted_key. This code path is reachable from ParseEncrypted() / ParseEncryptedJSON() / ParseEncryptedCompact() followed by Decrypt() on the resulting object. Note that the parse functions take a list of accepted key algorithms. If the accepted key algorithms do not include any key wrapping algorithms, parsing will fail and the application will be unaffected. This panic is also reachable by calling cipher.KeyUnwrap() directly with any ciphertext parameter less than 16 bytes long, but calling this function directly is less common. Panics can lead to denial of service. This vulnerability is fixed in 4.1.4 and 3.0.5.

Затронутые продукты
openSUSE Leap 16.0:hauler-1.4.3-bp160.1.1
Ссылки

Описание

Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Versions 2.0.5 and below contain an authorization bypass vulnerability in the VerifyTimestampResponse function. VerifyTimestampResponse correctly verifies the certificate chain signature, but the TSA-specific constraint checks in VerifyLeafCert uses the first non-CA certificate from the PKCS#7 certificate bag instead of the leaf certificate from the verified chain. An attacker can exploit this by prepending a forged certificate to the certificate bag while the message is signed with an authorized key, causing the library to validate the signature against one certificate but perform authorization checks against another. This vulnerability only affects users of the timestamp-authority/v2/pkg/verification package and does not affect the timestamp-authority service itself or sigstore-go. The issue has been fixed in version 2.0.6.

Затронутые продукты
openSUSE Leap 16.0:hauler-1.4.3-bp160.1.1
Ссылки