cve.bz

CVE-2024-20321 cisco nx-os: Uncontrolled Resource Consumption

8.6 highEPSS 0.7%

High (8.6) in cisco nx-os. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
A vulnerability in the External Border Gateway Protocol (eBGP) implementation of Cisco NX-OS Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability exists because eBGP traffic is mapped to a shared hardware rate-limiter queue. An attacker could exploit this vulnerability by sending large amounts of network traffic with certain characteristics through an affected device. A successful exploit could allow the attacker to cause eBGP neighbor sessions to be dropped, leading to a DoS condition in the network.

Severity

CVSS 3.1

8.6 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 54th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2024-03-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-770 Allocation of Resources Without Limits or Throttling
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-20321 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-20321?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-20321?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-20321 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
cisco:nx-os7.0(3)f1(1)
cisco:nx-os7.0(3)f2(1)
cisco:nx-os7.0(3)f2(2)
cisco:nx-os7.0(3)f3(1)
cisco:nx-os7.0(3)f3(2)
cisco:nx-os7.0(3)f3(3)
cisco:nx-os7.0(3)f3(3a)
cisco:nx-os7.0(3)f3(3c)
cisco:nx-os7.0(3)f3(4)
cisco:nx-os7.0(3)f3(5)
cisco:nx-os9.2(1)
cisco:nx-os9.2(2)
cisco:nx-os9.2(2t)
cisco:nx-os9.2(2v)
cisco:nx-os9.2(3)
cisco:nx-os9.2(4)
cisco:nx-os9.3(1)
cisco:nx-os9.3(2)
cisco:nx-os9.3(3)
cisco:nx-os9.3(4)
cisco:nx-os9.3(5)
cisco:nx-os9.3(6)
cisco:nx-os9.3(7)
cisco:nx-os9.3(7a)
cisco:nx-os9.3(8)
cisco:nx-os9.3(9)
cisco:nx-os9.3(10)
cisco:nx-os9.3(11)
cisco:nx-os9.3(12)
cisco:nx-os10.1(1)
cisco:nx-os10.1(2)
cisco:nx-os10.1(2t)
cisco:nx-os10.2(1)
cisco:nx-os10.2(1q)
cisco:nx-os10.2(2)
cisco:nx-os10.2(3)
cisco:nx-os10.2(3t)
cisco:nx-os10.2(3v)
cisco:nx-os10.2(4)
cisco:nx-os10.2(5)
cisco:nx-os10.2(6)
cisco:nx-os10.3(1)
cisco:nx-os10.3(2)
cisco:nx-os10.3(3)
cisco:nx-os10.3(4a)
cisco:nx-os10.3(99w)
cisco:nx-os10.3(99x)
cisco:nx-os10.4(1)

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON