Access of Resource Using Incompatible Type ('Type Confusion') Affecting edk2-aarch64 package, versions <0:20231122-6.el9_4.4


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.05% (18th percentile)

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 Learn

Learn about Access of Resource Using Incompatible Type ('Type Confusion') vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL9-EDK2AARCH64-8349913
  • published7 Nov 2024
  • disclosed4 Sept 2024

Introduced: 4 Sep 2024

CVE-2024-6119  (opens in a new tab)
CWE-843  (opens in a new tab)

How to fix?

Upgrade RHEL:9 edk2-aarch64 to version 0:20231122-6.el9_4.4 or higher.
This issue was patched in RHSA-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 RHEL. See How to fix? for RHEL: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.

CVSS Scores

version 3.1