edk2-20240524-6.el9
エラータID: AXSA:2024-9428:12
以下項目について対処しました。
[Security Fix]
- OpenSSL の POLY1305 MAC (メッセージ認証コード) の実装
には、PowerPC アーキテクチャの CPU を利用している場合、
CPU のレジスタの情報を破壊してしまう問題があるため、
リモートの攻撃者により、POLY1305 MAC の利用を介して、
サービス拒否攻撃 (クラッシュの発生など) を可能とする
脆弱性が存在します。(CVE-2023-6129)
- OpenSSL の EVP_PKEY_public_check() 関数には、大きすぎる
n 値を持つ RSA 公開鍵の検証処理に長い処理時間を要してしまう
問題があるため、リモートの攻撃者により、openssl pkey
コマンドや "-pubin"、"-check" オプションなどの利用を介して、
サービス拒否攻撃を可能とする脆弱性が存在します。
(CVE-2023-6237)
- OpenSSL の PKCS12_parse() 関数、PKCS12_unpack_p7data()
関数、PKCS12_unpack_p7encdata() 関数、
PKCS12_unpack_authsafes() 関数、および PKCS12_newpass()
関数には、特定のフィールドの NULL 値のチェック処理の欠落
に起因した NULL ポインタデリファレンスの問題があるため、
ローカルの攻撃者により、細工された PKCS12 形式のファイル
の処理を介して、サービス拒否攻撃 (クラッシュの発生) を
可能とする脆弱性が存在します。(CVE-2024-0727)
- EDK II には、32 ビット幅の符号なし整数型の変数のオーバー
フローに起因したゼロ除算の問題があるため、ローカルの攻撃者
により、ACPI S3 ステート状態への遷移を介して、サービス拒否
攻撃を可能とする脆弱性が存在します。(CVE-2024-1298)
パッケージをアップデートしてください。
Issue summary: The POLY1305 MAC (message authentication code) implementation contains a bug that might corrupt the internal state of applications running on PowerPC CPU based platforms if the CPU provides vector instructions. Impact summary: If an attacker can influence whether the POLY1305 MAC algorithm is used, the application state might be corrupted with various application dependent consequences. The POLY1305 MAC (message authentication code) implementation in OpenSSL for PowerPC CPUs restores the contents of vector registers in a different order than they are saved. Thus the contents of some of these vector registers are corrupted when returning to the caller. The vulnerable code is used only on newer PowerPC processors supporting the PowerISA 2.07 instructions. The consequences of this kind of internal application state corruption can be various - from no consequences, if the calling application does not depend on the contents of non-volatile XMM registers at all, to the worst consequences, where the attacker could get complete control of the application process. However unless the compiler uses the vector registers for storing pointers, the most likely consequence, if any, would be an incorrect result of some application dependent calculations or a crash leading to a denial of service. The POLY1305 MAC algorithm is most frequently used as part of the CHACHA20-POLY1305 AEAD (authenticated encryption with associated data) algorithm. The most common usage of this AEAD cipher is with TLS protocol versions 1.2 and 1.3. If this cipher is enabled on the server a malicious client can influence whether this AEAD cipher is used. This implies that TLS server applications using OpenSSL can be potentially impacted. However we are currently not aware of any concrete application that would be affected by this issue therefore we consider this a Low severity security issue.
Issue summary: Checking excessively long invalid RSA public keys may take a long time. Impact summary: Applications that use the function EVP_PKEY_public_check() to check RSA public keys may experience long delays. Where the key that is being checked has been obtained from an untrusted source this may lead to a Denial of Service. When function EVP_PKEY_public_check() is called on RSA public keys, a computation is done to confirm that the RSA modulus, n, is composite. For valid RSA keys, n is a product of two or more large primes and this computation completes quickly. However, if n is an overly large prime, then this computation would take a long time. An application that calls EVP_PKEY_public_check() and supplies an RSA key obtained from an untrusted source could be vulnerable to a Denial of Service attack. The function EVP_PKEY_public_check() is not called from other OpenSSL functions however it is called from the OpenSSL pkey command line application. For that reason that application is also vulnerable if used with the '-pubin' and '-check' options on untrusted data. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.
Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly. A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue. OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass(). We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.
EDK2 contains a vulnerability when S3 sleep is activated where an Attacker may cause a Division-By-Zero due to a UNIT32 overflow via local access. A successful exploit of this vulnerability may lead to a loss of Availability.
N/A
SRPMS
- edk2-20240524-6.el9.src.rpm
MD5: 0bacc82f0b925c56799d51659a43a062
SHA-256: 4c7e6cbfe85a51b93fdd88f448174b524c6a448793bb41b59df9c5b3072bfa84
Size: 45.46 MB
Asianux Server 9 for x86_64
- edk2-ovmf-20240524-6.el9.noarch.rpm
MD5: 769f2ce848d2a01236463df124e022e0
SHA-256: e3fcd89a22dc182f3d1e3bc120b55d79e28301cb575e9dd7f7e6861f16c186a8
Size: 6.02 MB - edk2-tools-20240524-6.el9.x86_64.rpm
MD5: 71e571727c9e1c91b050698ab63d2d06
SHA-256: a1eb3a410f45aea5678a955764e5a9c55e90f7ab11b98b4453dd22017f58513e
Size: 425.19 kB - edk2-tools-doc-20240524-6.el9.noarch.rpm
MD5: a04962af0f73729092c6ccf44ea5612b
SHA-256: 25651bfdd76fe3d4a672061f90f4523ee450863c7d04c4958e6b219dafb841d7
Size: 96.10 kB