# CVE-2023-41376: Other in n/a

> Attackers can cause denial of service in Nokia SR OS by exploiting mishandled BGP path attributes when error-handling update-fault-tolerance is disabled.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 29 Aug 2023
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-q4c3-fmw8-m6gp

## What is CVE-2023-41376?

CVE-2023-41376 is a high-severity vulnerability in n/a, published on 29 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nokia Service Router Operating System (SR OS) 22.10 and SR Linux, when error-handling update-fault-tolerance is not enabled, mishandle BGP path attributes.

Weakness: CWE-670 (Always-Incorrect Control Flow Implementation)

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

It affects 2 products.


Products: Nokia Service Router Linux, Nokia Service Router Operating System.

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

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

## Is CVE-2023-41376 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41376 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-41376 is a high-severity vulnerability in n/a, published on 29 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41376 exists.

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-41376/ (Markdown: https://insights.sbomify.com/CVE-2023-41376/index.md)
```

## Sources

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

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