# CVE-2024-41184: Integer overflow in n/a

> An integer overflow in Keepalived's IP sets handler can cause a denial of service, requiring a specific empty IP set name configuration.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 18 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** ALSA-2025:0743, ALSA-2025:0917, AZL-43419, AZL-43423, DEBIAN-CVE-2024-41184, GHSA-343m-v77v-mv8r, RHSA-2025:0743, RHSA-2025:0917, RLSA-2025:0743, RLSA-2025:0917, SUSE-SU-2024:3031-1, SUSE-SU-2024:3633-1, SUSE-SU-2024:3634-1, SUSE-SU-2024:3658-1, SUSE-SU-2025:20039-1, UBUNTU-CVE-2024-41184, openSUSE-SU-2024:14332-1

## What is CVE-2024-41184?

CVE-2024-41184 is a critical vulnerability in n/a, published on 18 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the vrrp_ipsets_handler handler (fglobal_parser.c) of keepalived through 2.3.1, an integer overflow can occur. NOTE: this CVE Record might not be worthwhile because an empty ipset name must be configured by the user.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keepalived` | AlmaLinux:8 | All versions | 2.1.5-10.el8_10 |
| `keepalived` | AlmaLinux:9 | All versions | 2.2.8-4.el9_5 |
| `keepalived` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.5-10.el8_10 |
| `keepalived-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.5-10.el8_10 |
| `keepalived-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.1.5-10.el8_10 |
| `keepalived` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.2.8-4.el9_5 |
| `keepalived-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.2.8-4.el9_5 |
| `keepalived-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.2.8-4.el9_5 |
| `keepalived` | Rocky Linux:8 | All versions | 0:2.1.5-10.el8_10 |
| `keepalived` | Rocky Linux:9 | All versions | 0:2.2.8-4.el9_5 |
| `keepalived` | SUSE:Linux Enterprise High Availability Extension 15 SP2 | All versions | 2.0.19-150100.3.9.1 |
| `keepalived` | SUSE:Linux Enterprise High Availability Extension 15 SP3 | All versions | 2.0.19-150100.3.9.1 |
| `keepalived` | SUSE:Linux Enterprise High Availability Extension 15 SP4 | All versions | 2.2.2-150400.3.10.1 |
| `keepalived` | SUSE:Linux Enterprise High Availability Extension 15 SP5 | All versions | 2.2.2-150500.8.5.1 |
| `keepalived` | SUSE:Linux Enterprise High Availability Extension 15 SP6 | All versions | 2.2.8-150600.3.5.1 |
| `keepalived` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.2.2-150400.3.10.1 |
| `keepalived` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.2.2-150400.3.10.1 |
| `keepalived` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.2.2-150500.8.5.1 |
| `keepalived` | SUSE:Linux Micro 6.0 | All versions | 2.2.8-2.1 |
| `keepalived` | openSUSE:Leap 15.5 | All versions | 2.2.2-150500.8.5.1 |
| `keepalived` | openSUSE:Leap 15.6 | All versions | 2.2.8-150600.3.5.1 |
| `keepalived` | openSUSE:Leap Micro 5.5 | All versions | 2.2.2-150500.8.5.1 |
| `keepalived` | openSUSE:Tumbleweed | All versions | 2.3.1+git59.b6681f98-1.1 |

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

Apply the vendor's patch.

## Is CVE-2024-41184 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41184 is a critical vulnerability in n/a, published on 18 Jul 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-41184 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-41184/ (Markdown: https://insights.sbomify.com/CVE-2024-41184/index.md)
```

## Sources

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

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