dbcve.org
Ios XeOperating system · Cisco

CVE-2024-20464

HIGH · 8.6 CVSS v3.1 Published 2024-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/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
A vulnerability in the Protocol Independent Multicast (PIM) feature of Cisco IOS XE Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to insufficient validation of received IPv4 PIMv2 packets. An attacker could exploit this vulnerability by sending a crafted PIMv2 packet to a PIM-enabled interface on an affected device. A successful exploit could allow the attacker to cause an affected device to reload, resulting in a DoS condition. Note: This vulnerability can be exploited with either an IPv4 multicast or unicast packet.

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 · high confidence

A vulnerability in Cisco IOS XE's Protocol Independent Multicast (PIM) feature stems from insufficient validation of incoming IPv4 PIMv2 packets. An unauthenticated remote attacker can send crafted PIMv2 packets (via multicast or unicast) to a PIM-enabled interface, causing the affected device to reload and result in denial of service.

MitigationApply the Cisco IOS XE security patch for this vulnerability. As a defense-in-depth measure, disable PIM on unused interfaces and restrict PIM traffic at network boundaries.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ios XeOperating system
Affected:= 17.13.1= 17.13.1a

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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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. Identify the installed Cisco IOS XE version
    Execute 'show version' or 'show version | include IOS XE' on the device CLI to retrieve the running IOS XE version number
    Affected if The displayed version is exactly 17.13.1 or 17.13.1a
  2. Verify if PIM is enabled on any interface
    Execute 'show ip pim interface' or 'show running-config | include ip pim' to list interfaces with PIM enabled
    Affected if One or more interfaces have PIM enabled (the vulnerability requires PIM to be active on the targeted interface)
  3. Confirm IPv4 PIM configuration
    Execute 'show ip pim interface [interface]' to verify IPv4 PIM is active on specific interfaces
    Affected if IPv4 PIM is shown as active on any interface, meaning incoming PIMv2 packets can be processed

You are affected if your device runs IOS XE version 17.13.1 or 17.13.1a AND has IPv4 PIM enabled on at least one interface, allowing external PIMv2 packets to reach that interface.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco IOS XE security patch for this vulnerability. As a defense-in-depth measure, disable PIM on unused interfaces and restrict PIM traffic at network boundaries.

Recommended fix Moderate confidence

Upgrade to a Cisco IOS XE release later than 17.13.1a (refer to Cisco Security Advisory for exact fixed version)

  1. 1. Verify the current Cisco IOS XE version on the affected device using 'show version'
  2. 2. Check the Cisco Security Advisory (cisco.com) for CVE-2024-20464 to identify the specific fixed release
  3. 3. Plan a maintenance window for the upgrade
  4. 4. Back up the current device configuration
  5. 5. Upgrade to the fixed IOS XE release identified in the Cisco Security Advisory
  6. 6. Verify the upgrade was successful using 'show version'
  7. 7. Confirm PIM functionality is restored and the device is stable
Caveat Standard upgrade risks apply - ensure configuration compatibility and plan for potential reload

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ios Xe Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20464 — 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-20464 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