# CVE-2024-6119: Possible denial of service in X.509 name checks > Attackers can cause denial of service in applications performing X.509 name checks by triggering an invalid memory read. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 3 Sep 2024 - **Updated:** 15 Oct 2026 - **Also known as:** ALPINE-CVE-2024-6119, ALSA-2024:6783, ALSA-2024:8935, AZL-48535, AZL-48747, AZL-48792, AZL-48798, AZL-78570, BELL-CVE-2024-6119, CLEANSTART-2026-KP48675, CLSA-2024-1725524582, CLSA-2024-1729546540, DEBIAN-CVE-2024-6119, DSA-5764-1, GHSA-7m4m-pwhv-49c5, JLSEC-2026-253, MGASA-2024-0291, OESA-2024-2131, OESA-2024-2179, RHSA-2024:6783, RHSA-2024:8935, RLSA-2024:6783, RLSA-2024:8935, SUSE-SU-2024:3105-1, SUSE-SU-2024:3106-1, SUSE-SU-2024:3107-1, SUSE-SU-2025:1516-1, UBUNTU-CVE-2024-6119, USN-6986-1, openSUSE-SU-2024:14317-1 ## What is CVE-2024-6119? CVE-2024-6119 is a high-severity denial of service vulnerability in Netapp Active Iq Unified Manager, published on 3 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-843 (Access of Resource Using Incompatible Type) ## Which versions are affected by CVE-2024-6119? It affects 19 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `edk2-aarch64` | AlmaLinux:9 | All versions | 20231122-6.el9_4.4 | | `edk2-ovmf` | AlmaLinux:9 | All versions | 20231122-6.el9_4.4 | | `edk2-tools` | AlmaLinux:9 | All versions | 20231122-6.el9_4.4 | | `edk2-tools-doc` | AlmaLinux:9 | All versions | 20231122-6.el9_4.4 | | `openssl` | AlmaLinux:9 | All versions | 1:3.0.7-28.el9_4 | | `openssl-devel` | AlmaLinux:9 | All versions | 1:3.0.7-28.el9_4 | | `openssl-libs` | AlmaLinux:9 | All versions | 1:3.0.7-28.el9_4 | | `openssl-perl` | AlmaLinux:9 | All versions | 1:3.0.7-28.el9_4 | | `edk2` | Red Hat:enterprise_linux:9::appstream | All versions | 0:20231122-6.el9_4.4 | | `edk2-aarch64` | Red Hat:enterprise_linux:9::appstream | All versions | 0:20231122-6.el9_4.4 | | `edk2-ovmf` | Red Hat:enterprise_linux:9::appstream | All versions | 0:20231122-6.el9_4.4 | | `openssl-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:3.0.7-28.el9_4 | | `openssl-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 1:3.0.7-28.el9_4 | | `openssl-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 1:3.0.7-28.el9_4 | | `openssl-libs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:3.0.7-28.el9_4 | | `openssl-perl` | Red Hat:enterprise_linux:9::appstream | All versions | 1:3.0.7-28.el9_4 | | `openssl` | Red Hat:enterprise_linux:9::baseos | All versions | 1:3.0.7-28.el9_4 | | `openssl-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 1:3.0.7-28.el9_4 | | `openssl-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 1:3.0.7-28.el9_4 | | `openssl-libs` | Red Hat:enterprise_linux:9::baseos | All versions | 1:3.0.7-28.el9_4 | | `openssl-libs-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 1:3.0.7-28.el9_4 | | `edk2-aarch64` | Red Hat:enterprise_linux:9::crb | All versions | 0:20231122-6.el9_4.4 | | `edk2-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:20231122-6.el9_4.4 | | `edk2-ovmf` | Red Hat:enterprise_linux:9::crb | All versions | 0:20231122-6.el9_4.4 | | `edk2-tools` | Red Hat:enterprise_linux:9::crb | All versions | 0:20231122-6.el9_4.4 | | `edk2-tools-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:20231122-6.el9_4.4 | | `edk2-tools-doc` | Red Hat:enterprise_linux:9::crb | All versions | 0:20231122-6.el9_4.4 | | `edk2` | Rocky Linux:9 | All versions | 0:20231122-6.el9_4.4 | | `openssl` | Rocky Linux:9 | All versions | 1:3.0.7-28.el9_4 | | `openssl-3` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 3.0.8-150400.4.63.1 | | `openssl-3` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 3.0.8-150400.4.63.1 | | `openssl-3` | SUSE:Linux Enterprise Micro 5.3 | All versions | 3.0.8-150400.4.63.1 | | `openssl-3` | SUSE:Linux Enterprise Micro 5.4 | All versions | 3.0.8-150400.4.63.1 | | `openssl-3` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 3.0.8-150500.5.42.1 | | `openssl-3` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 3.1.4-150600.5.15.1 | | `openssl-3` | SUSE:Linux Enterprise Module for Certifications 15 SP7 | All versions | 3.1.4-150600.5.15.1 | | `openssl-3` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 3.0.8-150400.4.63.1 | | `openssl-3` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 3.0.8-150400.4.63.1 | | `openssl-3` | SUSE:Manager Proxy 4.3 | All versions | 3.0.8-150400.4.63.1 | | `openssl-3` | SUSE:Manager Server 4.3 | All versions | 3.0.8-150400.4.63.1 | Products: Netapp 500f Firmware, Netapp A250 Firmware, Netapp Active Iq Unified Manager, Netapp Bootstrap Os, Netapp Brocade Fabric Operating System, Netapp C250 Firmware, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500s Firmware, Netapp H610c Firmware, Netapp H610s Firmware, Netapp H615c, Netapp H700s Firmware, Netapp Management Services for Element Software and Netapp Hci, Netapp Ontap 9, Netapp Ontap Select Deploy Administration Utility, Netapp Ontap Tools, Openssl Openssl. ## How do I fix CVE-2024-6119? Apply the vendor's patch. ## Is CVE-2024-6119 being exploited? There is no known exploitation of CVE-2024-6119 in the wild and no public exploit code. ## Other vulnerabilities in Netapp Active Iq Unified Manager - [CVE-2021-4044](https://insights.sbomify.com/CVE-2021-4044/): Invalid handling of X509_verify_cert() internal errors in libssl (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-6119 and fix it if it is affected. What it is: CVE-2024-6119 is a high-severity denial of service vulnerability in Netapp Active Iq Unified Manager, published on 3 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-6119 in the wild and no public exploit code. Affected product: Netapp Active Iq Unified Manager. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-6119/ (Markdown: https://insights.sbomify.com/CVE-2024-6119/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6119 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6119 - OSV: https://osv.dev/vulnerability/CVE-2024-6119 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-6119/ Summaries are generated and may contain mistakes; the official description above is the record.