Skip to main content
VulnerabilityPublished Updated

CVE-2024-41184: keepalived · Integer Overflow or Wraparound

Affects keepalivedSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.3.2 as a priority.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.3.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade acassen/keepalived to 2.3.2.

Affected software

ProductAffectedFixed in
GitHubacassen/keepalivedpkg:github/acassen/keepalivedOther threatsAffected
  • <2.3.2
Fixed in
  • 2.3.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-41184, organizations should immediately audit their keepalived configurations to ensure no empty ipset names are set, as this is the prerequisite for exploitation. Administrators should enforce strict validation of ipset names and avoid any configurations that could trigger the integer overflow. Monitoring and logging VRRP and keepalived activity can help detect anomalous behavior indicative of exploitation attempts. As a proactive measure, consider isolating keepalived instances from untrusted networks and restricting access to management interfaces. Employ network segmentation and firewall rules to limit exposure of VRRP services. Additionally, conducting vulnerability scans and penetration tests focusing on keepalived configurations can identify potential weaknesses. Finally, maintain regular backups and incident response plans to minimize impact in case of successful exploitation.

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.

References

Community reviews

Loading reviews…