# CVE-2025-20115: Cisco IOS XR Software Border Gateway Protocol Denial of Service Vulnerability

> Remote attackers can cause a denial of service in Cisco IOS XR by triggering memory corruption via crafted BGP confederation updates.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2025
- **Updated:** 21 Mar 2025
- **Also known as:** GHSA-rp6p-7xx7-cr6f

## What is CVE-2025-20115?

CVE-2025-20115 is a high-severity memory corruption vulnerability in Cisco Ios Xr, published on 12 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2025-20115?

It affects 1 product.


Products: Cisco Ios Xr.

## How do I fix CVE-2025-20115?

No fix has been published for CVE-2025-20115 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-20115 being exploited?

There is no known exploitation of CVE-2025-20115 in the wild and no public exploit code.

Public exploit code:

- Patch: Buffer overread (OpenSSL) (github_poc): https://github.com/gduma-phData/patch-CVE-2025-20115

## Other vulnerabilities in Cisco Ios Xr

- [CVE-2020-3118](https://insights.sbomify.com/CVE-2020-3118/): Cisco IOS XR Software Discovery Protocol Format String (high 8.8, exploited in the wild)
- [CVE-2020-3569](https://insights.sbomify.com/CVE-2020-3569/): Cisco IOS XR Software DVMRP Memory Exhaustion (high 8.6, exploited in the wild)
- [CVE-2020-3566](https://insights.sbomify.com/CVE-2020-3566/): Cisco IOS XR Software DVMRP Memory Exhaustion (high 8.6, exploited in the wild)
- [CVE-2010-3035](https://insights.sbomify.com/CVE-2010-3035/): Cisco IOS XR Border Gateway Protocol (BGP) Denial-of-Service (high 7.5, exploited in the wild)
- [CVE-2022-20821](https://insights.sbomify.com/CVE-2022-20821/): Cisco IOS XR Open Port (medium 6.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-20115 and fix it if it is affected.

What it is: CVE-2025-20115 is a high-severity memory corruption vulnerability in Cisco Ios Xr, published on 12 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-20115 in the wild and no public exploit code.

Affected product: Cisco Ios Xr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-20115/ (Markdown: https://insights.sbomify.com/CVE-2025-20115/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-20115
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-20115
- OSV: https://osv.dev/vulnerability/CVE-2025-20115

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-20115/
Summaries are generated and may contain mistakes; the official description above is the record.