dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2024-41184

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Integer overflow vulnerability in the vrrp_ipsets_handler function in global_parser.c of keepalived through version 2.3.1. The overflow occurs during ipset name handling. However, exploitation requires a user to explicitly configure an empty ipset name, which is non-standard and unusual configuration, significantly limiting practical attack surface.

MitigationAvoid configuring empty ipset names in keepalived configuration; if available, upgrade to a patched version that addresses the integer overflow in the VRRP ipset handler.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed keepalived version
    Run 'keepalived --version' or check the package manager for the installed version
    Affected if The installed version is 2.3.1 or earlier (any version through 2.3.1)
  2. Locate keepalived configuration files
    Check common locations such as /etc/keepalived/keepalived.conf, /etc/keepalived.conf, or search for 'keepalived.conf' on the system
    Affected if A keepalived configuration file exists on the system
  3. Identify VRRP ipset configuration
    Search the configuration file for 'ipset' keywords, particularly within VRRP instances or global definitions
    Affected if IPset configuration is present in the keepalived configuration
  4. Check for empty ipset names
    Inspect any ipset entries found and verify if any specify an empty string as the ipset name (for example, ipset = "" or similar syntax)
    Affected if Any ipset entry explicitly uses an empty name value (zero-length string)

A system is affected only if it runs keepalived version 2.3.1 or earlier AND has an explicitly configured empty ipset name in the VRRP configuration section.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid configuring empty ipset names in keepalived configuration; if available, upgrade to a patched version that addresses the integer overflow in the VRRP ipset handler.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41184 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-41184 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data