EN

CVE-2025-20115

High
8.6
0.05.010.0
Year
2025
Published
Mar 12, 2025
Known Affected Devices
0
CVSS Score
8.6

What is CVE-2025-20115?

A vulnerability in confederation implementation for the Border Gateway Protocol (BGP) in Cisco IOS XR Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition. This vulnerability is due to a memory corruption that occurs when a BGP update is created with an AS_CONFED_SEQUENCE attribute that has 255 autonomous system numbers (AS numbers). An attacker could exploit this vulnerability by sending a crafted BGP update message, or the network could be designed in such a manner that the AS_CONFED_SEQUENCE attribute grows to 255 AS numbers or more. A successful exploit could allow the attacker to cause memory corruption, which may cause the BGP process to restart, resulting in a DoS condition. To exploit this vulnerability, an attacker must control a BGP confederation speaker within the same autonomous system as the victim, or the network must be designed in such a manner that the AS_CONFED_SEQUENCE attribute grows to 255 AS numbers or more.

CVSS Vector Breakdown

CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
AV
Attack Vector
Network

Exploitable remotely over the network without requiring access to the local system.

AC
Attack Complexity
Low

No special conditions required. Exploit can be performed reliably and repeatedly.

PR
Privileges Required
None

No authentication required. Any anonymous user can exploit this vulnerability.

UI
User Interaction
None

No user interaction required. Exploit runs without any victim action.

S
Scope
Changed

Exploiting the vulnerability can affect other components beyond the vulnerable one.

C
Confidentiality Impact
None

No confidentiality impact. Sensitive data is not exposed.

I
Integrity Impact
None

No integrity impact. Data cannot be modified.

A
Availability Impact
High

Complete denial of service. The component becomes fully unavailable.

Known Affected Devices

Cisco Cisco ISR 4451 Cisco Cisco ISR 4461 Cisco Cisco ISR 927 Cisco Cisco ISR 931 Cisco Cisco ISR 951 Cisco Cisco ASR 1001-HX Cisco Cisco ASR 1002-X Cisco Cisco ASR 1002-HX Cisco Cisco ASR 1004 Cisco Cisco ASR 1006-X Cisco Cisco ASR 1009-X Cisco Cisco ASR 1013 Cisco Cisco ASR 9001 Cisco Cisco ASR 9901 Cisco Cisco ASR 9910 Cisco Cisco ASR 9912 Cisco Cisco Catalyst 2960S-48TS-L Cisco Cisco Catalyst 2960X-24PSQ-L Cisco Cisco Catalyst 2960XR-24TS-I Cisco Cisco Catalyst 3560CX-8PC-S Cisco Cisco Catalyst 3650-48TS-L Cisco Cisco Catalyst 3750X-24P-S Cisco Cisco Catalyst 9200-24P Cisco Cisco Catalyst 9200-24T Cisco Cisco Catalyst 9200-48P Cisco Cisco Catalyst 9200-48T Cisco Cisco Catalyst 9200L-24P-4G Cisco Cisco Catalyst 9200L-24P-4X Cisco Cisco Catalyst 9200L-48P-4G Cisco Cisco Catalyst 9300-24U Cisco Cisco Catalyst 9300-24UX Cisco Cisco Catalyst 9300-48T Cisco Cisco Catalyst 9404R Cisco Cisco Catalyst 9500-32C Cisco Cisco Catalyst 9500-48Y4C Cisco Cisco Catalyst 9600-40YC Cisco Cisco Nexus 7004 Cisco Cisco Nexus 9372PX Cisco Cisco Nexus 9504 Cisco Cisco Catalyst 9120AXI Cisco Cisco Catalyst 9800-40 Cisco Cisco Catalyst 9800-80 Cisco Cisco Catalyst 9800-L-F

FAQ

How severe is CVE-2025-20115?

CVE-2025-20115 has a CVSS score of 8.6/10, rated as High. This is a high severity vulnerability and should be patched as soon as possible.

What does the CVSS score mean for CVE-2025-20115?

CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2025-20115 scores 8.6/10 (High). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.

Which devices are affected by CVE-2025-20115?

The list of devices confirmed to be affected by CVE-2025-20115 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.

How do I fix or mitigate CVE-2025-20115?

Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.