CVE-2024-41184: Integer Overflow

Published Jul 18, 2024
·
Updated

In the vrrpipsetshandler handler (fglobalparser.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.

Affected Software

1 affected component
Keepalived Keepalived<=2.3.1

Event History

Jul 18, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·01:15 AM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·01:20 AM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-41184?

CVE-2024-41184 has a medium severity rating due to potential integer overflow vulnerabilities.

2

How do I fix CVE-2024-41184?

To fix CVE-2024-41184, upgrade Keepalived to version 2.3.2 or later, where the vulnerability has been addressed.

3

What is the impact of CVE-2024-41184?

CVE-2024-41184 could potentially lead to application crashes or unexpected behavior due to integer overflow.

4

Who is affected by CVE-2024-41184?

CVE-2024-41184 affects users of Keepalived versions up to and including 2.3.1 who configure an empty ipset name.

5

Is CVE-2024-41184 easy to exploit?

While CVE-2024-41184 does require specific configuration of an empty ipset name, it remains a potential risk for systems using vulnerable versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203