# CVE-2024-45367: Optigo Networks ONS-S8 Spectra Aggregation Switch Weak Authentication

> Attackers can bypass authentication on Optigo Networks ONS-S8 switches due to an incomplete web server authentication process.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2024
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-r83m-8j4j-wqgc

## What is CVE-2024-45367?

CVE-2024-45367 is a critical authentication bypass vulnerability in Optigo Networks ONS-S8 Spectra Aggregation Switch, published on 3 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web server for ONS-S8 - Spectra Aggregation Switch includes an incomplete authentication process, which can lead to an attacker authenticating without a password.

Weakness: CWE-1390 (Weak Authentication)

## Which versions are affected by CVE-2024-45367?


## How do I fix CVE-2024-45367?

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

## Is CVE-2024-45367 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45367 and fix it if it is affected.

What it is: CVE-2024-45367 is a critical authentication bypass vulnerability in Optigo Networks ONS-S8 Spectra Aggregation Switch, published on 3 Oct 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-2024-45367 in the wild and no public exploit code.

Affected product: Optigo Networks ONS-S8 Spectra Aggregation Switch. 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-2024-45367/ (Markdown: https://insights.sbomify.com/CVE-2024-45367/index.md)
```

## Sources

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

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