# CVE-2017-15865: Information disclosure in n/a

> Remote attackers can obtain sensitive information via malformed BGP UPDATE packets due to mishandled attribute lengths in FRRouting.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rh69-rw6w-x274, SUSE-SU-2024:3524-1

## What is CVE-2017-15865?

CVE-2017-15865 is a high-severity vulnerability in n/a, published on 8 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

bgpd in FRRouting (FRR) before 2.0.2 and 3.x before 3.0.2, as used in Cumulus Linux before 3.4.3 and other products, allows remote attackers to obtain sensitive information via a malformed BGP UPDATE packet from a connected peer, which triggers transmission of up to a few thousand unintended bytes because of a mishandled attribute length, aka RN-690 (CM-18492).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-15865?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `frr` | SUSE:Enterprise Storage 7.1 | All versions | 7.4-150300.4.32.1 |
| `frr` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 7.4-150300.4.32.1 |
| `frr` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 7.4-150300.4.32.1 |
| `frr` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 7.4-150300.4.32.1 |
| `frr` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 7.4-150300.4.32.1 |
| `frr` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 7.4-150300.4.32.1 |
| `frr` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 7.4-150300.4.32.1 |
| `frr` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 7.4-150300.4.32.1 |
| `frr` | SUSE:Manager Proxy 4.3 | All versions | 7.4-150300.4.32.1 |
| `frr` | SUSE:Manager Server 4.3 | All versions | 7.4-150300.4.32.1 |

Products: Frrouting Frrouting.

## How do I fix CVE-2017-15865?

Upgrade to a fixed version.

## Is CVE-2017-15865 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-44070](https://insights.sbomify.com/CVE-2024-44070/): Denial of service in n/a (critical 9.8)
- [CVE-2023-38406](https://insights.sbomify.com/CVE-2023-38406/): bgpd/bgp_flowspec.c in FRRouting (FRR) before 8.4.3 mishandles an nlri length of zero, aka a "flowspec overflow." (critical 9.8)
- [CVE-2022-37035](https://insights.sbomify.com/CVE-2022-37035/): Use after free in n/a (high 8.1)
- [CVE-2022-26127](https://insights.sbomify.com/CVE-2022-26127/): Memory corruption in FRRouting (high 7.8)
- [CVE-2022-26128](https://insights.sbomify.com/CVE-2022-26128/): Memory corruption in FRRouting (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15865 and fix it if it is affected.

What it is: CVE-2017-15865 is a high-severity vulnerability in n/a, published on 8 Nov 2017. 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-2017-15865 in the wild and no public exploit code.

Affected product: n/a. 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-2017-15865/ (Markdown: https://insights.sbomify.com/CVE-2017-15865/index.md)
```

## Sources

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

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