Out-of-bounds Write Affecting edk2-tools-doc package, versions <0:20240524-6.el9_5
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-ALMALINUX9-EDK2TOOLSDOC-8383757
- published 18 Nov 2024
- disclosed 30 Apr 2024
Introduced: 30 Apr 2024
CVE-2023-6129 Open this link in a new tabHow to fix?
Upgrade AlmaLinux:9 edk2-tools-doc to version 0:20240524-6.el9_5 or higher.
This issue was patched in ALSA-2024:9088.
NVD Description
Note: Versions mentioned in the description apply only to the upstream edk2-tools-doc package and not the edk2-tools-doc package as distributed by AlmaLinux.
See How to fix? for AlmaLinux:9 relevant fixed versions and status.
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.
References
- https://errata.almalinux.org/9/ALSA-2024-2447.html
- https://errata.almalinux.org/9/ALSA-2024-9088.html
- https://access.redhat.com/security/cve/CVE-2023-6129
- https://access.redhat.com/errata/RHSA-2024:2447
- https://access.redhat.com/errata/RHSA-2024:9088
- http://www.openwall.com/lists/oss-security/2024/01/09/1
- http://www.openwall.com/lists/oss-security/2024/03/11/1
- https://security.netapp.com/advisory/ntap-20240216-0009/
- https://security.netapp.com/advisory/ntap-20240426-0008/
- https://security.netapp.com/advisory/ntap-20240426-0013/
- https://security.netapp.com/advisory/ntap-20240503-0011/
- https://github.com/openssl/openssl/commit/050d26383d4e264966fb83428e72d5d48f402d35
- https://github.com/openssl/openssl/commit/5b139f95c9a47a55a0c54100f3837b1eee942b04
- https://github.com/openssl/openssl/commit/f3fc5808fe9ff74042d639839610d03b8fdcc015
- https://www.openssl.org/news/secadv/20240109.txt