cve.bz

CVE-2021-1230 cisco nx-os: Improper Handling of Parameters

7.5 highEPSS 1.5%

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

On this page
A vulnerability with the Border Gateway Protocol (BGP) for Cisco Nexus 9000 Series Fabric Switches in Application Centric Infrastructure (ACI) mode could allow an unauthenticated, remote attacker to cause a routing process to crash, which could lead to a denial of service (DoS) condition. This vulnerability is due to an issue with the installation of routes upon receipt of a BGP update. An attacker could exploit this vulnerability by sending a crafted BGP update to an affected device. A successful exploit could allow the attacker to cause the routing process to crash, which could cause the device to reload. This vulnerability applies to both Internal BGP (IBGP) and External BGP (EBGP). Note: The Cisco implementation of BGP accepts incoming BGP traffic from explicitly configured peers only. To exploit this vulnerability, an attacker would need to send a specific BGP update message over an established TCP connection that appears to come from a trusted BGP peer.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
1.5% (unchanged from 1.5% a week ago; 1.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 76th 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-11-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-233 Improper Handling of Parameters
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-2021-1230 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-1230?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-1230?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-2021-1230 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-os12.0(1m)
cisco:nx-os12.0(1n)
cisco:nx-os12.0(1o)
cisco:nx-os12.0(1p)
cisco:nx-os12.0(1q)
cisco:nx-os12.0(1r)
cisco:nx-os12.0(2f)
cisco:nx-os12.0(2g)
cisco:nx-os12.0(2h)
cisco:nx-os12.0(2l)
cisco:nx-os12.0(2m)
cisco:nx-os12.0(2n)
cisco:nx-os12.0(2o)
cisco:nx-os12.1(1h)
cisco:nx-os12.1(1i)
cisco:nx-os12.1(2e)
cisco:nx-os12.1(2g)
cisco:nx-os12.1(2k)
cisco:nx-os12.1(3g)
cisco:nx-os12.1(3h)
cisco:nx-os12.1(3j)
cisco:nx-os12.1(4a)
cisco:nx-os12.2(1k)
cisco:nx-os12.2(1n)
cisco:nx-os12.2(1o)
cisco:nx-os12.2(2e)
cisco:nx-os12.2(2f)
cisco:nx-os12.2(2i)
cisco:nx-os12.2(2j)
cisco:nx-os12.2(2k)
cisco:nx-os12.2(2q)
cisco:nx-os12.2(3j)
cisco:nx-os12.2(3p)
cisco:nx-os12.2(3r)
cisco:nx-os12.2(3s)
cisco:nx-os12.2(3t)
cisco:nx-os12.2(4f)
cisco:nx-os12.2(4p)
cisco:nx-os12.2(4q)
cisco:nx-os12.2(4r)
cisco:nx-os12.3(1e)
cisco:nx-os12.3(1f)
cisco:nx-os12.3(1i)
cisco:nx-os12.3(1l)
cisco:nx-os12.3(1o)
cisco:nx-os12.3(1p)
cisco:nx-os13.0(1k)
cisco:nx-os13.0(2h)
cisco:nx-os13.0(2k)
cisco:nx-os13.0(2n)
cisco:nx-os13.1(1i)
cisco:nx-os13.1(2m)
cisco:nx-os13.1(2o)
cisco:nx-os13.1(2p)
cisco:nx-os13.1(2q)
cisco:nx-os13.1(2s)
cisco:nx-os13.1(2t)
cisco:nx-os13.1(2u)
cisco:nx-os13.1(2v)
cisco:nx-os13.2(1l)
cisco:nx-os13.2(1m)
cisco:nx-os13.2(2l)
cisco:nx-os13.2(2o)
cisco:nx-os13.2(3i)
cisco:nx-os13.2(3j)
cisco:nx-os13.2(3n)
cisco:nx-os13.2(3o)
cisco:nx-os13.2(3r)
cisco:nx-os13.2(3s)
cisco:nx-os13.2(4d)
cisco:nx-os13.2(4e)
cisco:nx-os13.2(5d)
cisco:nx-os13.2(5e)
cisco:nx-os13.2(5f)
cisco:nx-os13.2(6i)
cisco:nx-os13.2(7f)
cisco:nx-os13.2(7k)
cisco:nx-os13.2(8d)
cisco:nx-os13.2(9b)
cisco:nx-os13.2(9f)
cisco:nx-os13.2(9h)
cisco:nx-os13.2(41d)
cisco:nx-os14.0(1h)
cisco:nx-os14.0(2c)
cisco:nx-os14.0(3c)
cisco:nx-os14.0(3d)
cisco:nx-os14.1(1i)
cisco:nx-os14.1(1j)
cisco:nx-os14.1(1k)
cisco:nx-os14.1(1l)
cisco:nx-os14.1(2g)
cisco:nx-os14.1(2m)
cisco:nx-os14.1(2o)
cisco:nx-os14.1(2s)
cisco:nx-os14.1(2u)
cisco:nx-os14.1(2w)
cisco:nx-os14.1(2x)
cisco:nx-os14.2(1i)
cisco:nx-os14.2(1j)
cisco:nx-os14.2(1l)
cisco:nx-os14.2(2e)
cisco:nx-os14.2(2f)
cisco:nx-os14.2(2g)

Attack patterns (CAPEC)

  • CAPEC-39 Manipulating Opaque Client-based Data Tokens Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON