CVE-2024-6119 Affecting edk2-aarch64 package, versions <0:20231122-6.el9_4.4
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-EDK2AARCH64-8352947
- published 8 Nov 2024
- disclosed 18 Sep 2024
Introduced: 18 Sep 2024
CVE-2024-6119 Open this link in a new tabHow to fix?
Upgrade AlmaLinux:9
edk2-aarch64
to version 0:20231122-6.el9_4.4 or higher.
This issue was patched in ALSA-2024:8935
.
NVD Description
Note: Versions mentioned in the description apply only to the upstream edk2-aarch64
package and not the edk2-aarch64
package as distributed by AlmaLinux
.
See How to fix?
for AlmaLinux:9
relevant fixed versions and status.
Issue summary: Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process.
Impact summary: Abnormal termination of an application can a cause a denial of service.
Applications performing certificate name checks (e.g., TLS clients checking
server certificates) may attempt to read an invalid memory address when
comparing the expected name with an otherName
subject alternative name of an
X.509 certificate. This may result in an exception that terminates the
application program.
Note that basic certificate chain validation (signatures, dates, ...) is not affected, the denial of service can occur only when the application also specifies an expected DNS name, Email address or IP address.
TLS servers rarely solicit client certificates, and even when they do, they generally don't perform a name check against a reference identifier (expected identity), but rather extract the presented identity after checking the certificate chain. So TLS servers are generally not affected and the severity of the issue is Moderate.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
References
- https://errata.almalinux.org/9/ALSA-2024-6783.html
- https://errata.almalinux.org/9/ALSA-2024-8935.html
- https://access.redhat.com/security/cve/CVE-2024-6119
- https://access.redhat.com/errata/RHSA-2024:6783
- https://access.redhat.com/errata/RHSA-2024:8935
- https://github.com/openssl/openssl/commit/05f360d9e849a1b277db628f1f13083a7f8dd04f
- https://github.com/openssl/openssl/commit/06d1dc3fa96a2ba5a3e22735a033012aadc9f0d6
- https://github.com/openssl/openssl/commit/621f3729831b05ee828a3203eddb621d014ff2b2
- https://github.com/openssl/openssl/commit/7dfcee2cd2a63b2c64b9b4b0850be64cb695b0a0
- https://openssl-library.org/news/secadv/20240903.txt
- http://www.openwall.com/lists/oss-security/2024/09/03/4
- https://lists.freebsd.org/archives/freebsd-security/2024-September/000303.html
- https://security.netapp.com/advisory/ntap-20240912-0001/