# CVE-2024-41996: Denial of service in n/a

> Remote attackers can cause server-side resource exhaustion via expensive DHE calculations if the server allows DHE and validates public key order.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2024
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2024-41996, GHSA-h964-f4gx-gw3x, OESA-2025-2325, OESA-2025-2326, OESA-2025-2327, OESA-2026-3419, SUSE-SU-2024:3500-1, SUSE-SU-2024:3501-1, SUSE-SU-2024:3525-1, openSUSE-SU-2024:14366-1

## What is CVE-2024-41996?

CVE-2024-41996 is a high-severity denial of service vulnerability in n/a, published on 26 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2024-41996?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openssl-3` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 3.0.8-150400.4.66.1 |
| `openssl-3` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 3.0.8-150400.4.66.1 |
| `openssl-3` | SUSE:Linux Enterprise Micro 5.3 | All versions | 3.0.8-150400.4.66.1 |
| `openssl-3` | SUSE:Linux Enterprise Micro 5.4 | All versions | 3.0.8-150400.4.66.1 |
| `openssl-3` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 3.0.8-150500.5.45.1 |
| `openssl-3` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 3.1.4-150600.5.18.1 |
| `openssl-3` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 3.0.8-150400.4.66.1 |
| `openssl-3` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 3.0.8-150400.4.66.1 |
| `openssl-3` | SUSE:Manager Proxy 4.3 | All versions | 3.0.8-150400.4.66.1 |
| `openssl-3` | SUSE:Manager Server 4.3 | All versions | 3.0.8-150400.4.66.1 |
| `openssl-3` | openSUSE:Leap 15.5 | All versions | 3.0.8-150500.5.45.1 |
| `openssl-3` | openSUSE:Leap 15.6 | All versions | 3.1.4-150600.5.18.1 |
| `openssl-3` | openSUSE:Tumbleweed | All versions | 3.1.4-14.1 |

## How do I fix CVE-2024-41996?

Apply the vendor's patch.

## Is CVE-2024-41996 being exploited?

There is no known exploitation of CVE-2024-41996 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41996 and fix it if it is affected.

What it is: CVE-2024-41996 is a high-severity denial of service vulnerability in n/a, published on 26 Aug 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-41996 in the wild and no public exploit code.

Affected product: n/a. 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-41996/ (Markdown: https://insights.sbomify.com/CVE-2024-41996/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41996
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41996
- OSV: https://osv.dev/vulnerability/CVE-2024-41996

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-41996/
Summaries are generated and may contain mistakes; the official description above is the record.