buildah-1.43.1-1.el9
エラータID: AXSA:2026-1125:04
リリース日:
2026/06/30 Tuesday - 22:54
題名:
buildah-1.43.1-1.el9
影響のあるチャネル:
MIRACLE LINUX 9 for x86_64
Severity:
High
Description:
以下項目について対処しました。
[Security Fix]
- Go 言語向けの JOSE の key_wrap.go の cipher.KeyUnwrap() 関数
には、バッファサイズの算出処理の不備に起因してサイズがゼロもしくは
マイナス値のメモリ領域の割り当てを試行してしまう問題があるため、
リモートの攻撃者により、alg フィールドにおいてキーラッピングアルゴ
リズムが指定され、かつ encrypted_key フィールドが空となるように
巧妙に細工された JWE オブジェクトの入力を介して、サービス拒否攻撃
を可能とする脆弱性が存在します。(CVE-2026-34986)
解決策:
パッケージをアップデートしてください。
CVE:
CVE-2026-34986
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.
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.
追加情報:
N/A
ダウンロード:
SRPMS
- buildah-1.43.1-1.el9.src.rpm
MD5: 5e4d284ea5a49c60e6148abc10c663d3
SHA-256: fd1a033d795d1ac707ede498ba0e7b8ba059638751f26890a96ad361e475535a
Size: 11.17 MB
Asianux Server 9 for x86_64
- buildah-1.43.1-1.el9.x86_64.rpm
MD5: 9f618c82ea5b5f7cdfe363c352a1cf55
SHA-256: 6ea5a30317ec91f5353d0ba774cdb1dec8ef9619b3966a5ee0708e2a1236177e
Size: 10.62 MB - buildah-tests-1.43.1-1.el9.x86_64.rpm
MD5: b165eab1975f170ae617018119104dd7
SHA-256: f5bc2d629f0f154e5d8f4209fd14bccec0e5b4cd88230863885ccdc881d0d711
Size: 30.72 MB