CVE-2024-5564
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 · uneditedA vulnerability was found in libndp. This flaw allows a local malicious user to cause a buffer overflow in NetworkManager, triggered by sending a malformed IPv6 router advertisement packet. This issue occurred as libndp was not correctly validating the route length information.
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 confidenceA buffer overflow vulnerability exists in libndp's IPv6 router advertisement handling due to missing validation of route length information. A local attacker can send malformed IPv6 router advertisement packets to trigger this overflow in NetworkManager, potentially leading to code execution or service disruption.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify libndp installation and versionRun 'rpm -q libndp' (RHEL/Fedora) or 'dpkg -l libndp' (Debian/Ubuntu) to check if libndp is installed. If installed, run 'rpm -q --changelog libndp | head -20' or check the package changelog for entries related to route length validation or CVE-2024-5564.Affected if libndp is installed and the installed version predates the patched release containing route length validation fixes.
-
Verify NetworkManager uses libndp for IPv6Check if NetworkManager is linked against libndp by running 'ldd /usr/sbin/NetworkManager | grep libndp' or 'nmcli -v' to confirm NetworkManager is present and IPv6-capable.Affected if NetworkManager is installed and linked to libndp, making it vulnerable to malformed router advertisement packets.
-
Confirm IPv6 is enabled in the environmentRun 'ip -6 addr show' or 'cat /proc/sys/net/ipv6/conf/all/disable_ipv6' to check if IPv6 is active on any interfaces. Also run 'nmcli connection show' to list active network connections.Affected if IPv6 is enabled and NetworkManager is managing IPv6 connections, as the flaw is triggered through IPv6 router advertisement handling.
-
Inspect NetworkManager IPv6 configurationRun 'nmcli -f ipv6.method connection show' to see if IPv6 is set to 'auto' or 'dhcp' (router advertisement mode). Check 'nmcli device show' for interface IPv6 settings.Affected if NetworkManager is configured to accept router advertisements (ipv6.method set to 'auto' or 'dhcp'), allowing it to process incoming IPv6 router advertisements that could contain malformed route information.
The environment is affected if libndp is installed with a vulnerable version, NetworkManager is linked to it, and IPv6 is enabled with NetworkManager configured to process router advertisements.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate libndp to the patched version that properly validates route length information, and ensure NetworkManager is rebuilt against the fixed library. Verify IPv6 functionality after patching.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5564 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5564 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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