# CVE-2023-40457: Denial of service in n/a

> An unauthenticated remote attacker can cause a denial of service by resetting BGP sessions through mishandled attribute errors in ExtremeXOS.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Nov 2024
- **Updated:** 12 Nov 2024
- **Also known as:** GHSA-hwrr-qggh-2777

## What is CVE-2023-40457?

CVE-2023-40457 is a denial of service vulnerability in n/a, published on 10 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The BGP daemon in Extreme Networks ExtremeXOS (aka EXOS) 30.7.1.1 allows an attacker (who is not on a directly connected network) to cause a denial of service (BGP session reset) because of BGP attribute error mishandling (for attribute 21 and 25). NOTE: the vendor disputes this because it is "evaluating support for RFC 7606 as a future feature" and believes that "customers that have chosen to not require or implement RFC 7606 have done so willingly and with knowledge of what is needed to defend against these types of attacks."

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2023-40457?


## How do I fix CVE-2023-40457?

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

## Is CVE-2023-40457 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-40457 and fix it if it is affected.

What it is: CVE-2023-40457 is a denial of service vulnerability in n/a, published on 10 Nov 2024. 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-2023-40457 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-2023-40457/ (Markdown: https://insights.sbomify.com/CVE-2023-40457/index.md)
```

## Sources

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

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