# CVE-2023-22618: Privilege escalation in n/a

> Local attackers can escalate privileges to admin by manipulating web requests if security hardening rules are not applied on Nokia WaveLite devices.

- **Severity:** High 8.1 (`CVSS:3.1/AC:H/AV:L/A:H/C:H/I:H/PR:N/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2023
- **Updated:** 20 Sep 2024
- **Also known as:** GHSA-6jj2-r9fx-9gjp

## What is CVE-2023-22618?

CVE-2023-22618 is a high-severity vulnerability in n/a, published on 4 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

If Security Hardening guide rules are not followed, then Nokia WaveLite products allow a local user to create new users with administrative privileges by manipulating a web request. This affects (for example) WaveLite Metro 200 and Fan, WaveLite Metro 200 OPS and Fans, WaveLite Metro 200 and F2B fans, WaveLite Metro 200 OPS and F2B fans, WaveLite Metro 200 NE and F2B fans, and WaveLite Metro 200 NE OPS and F2B fans.

Weakness: CWE-284 (Improper Access Control)

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

It affects 6 products.


Products: Nokia Wavelite Metro 200 and F2b Fans Firmware, Nokia Wavelite Metro 200 and Fan Firmware, Nokia Wavelite Metro 200 Ne and F2b Fans Firmware, Nokia Wavelite Metro 200 Ne Ops and F2b Fans Firmware, Nokia Wavelite Metro 200 Ops and F2b Fans Firmware, Nokia Wavelite Metro 200 Ops and Fans Firmware.

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

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

## Is CVE-2023-22618 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-22618 is a high-severity vulnerability in n/a, published on 4 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-22618 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-22618/ (Markdown: https://insights.sbomify.com/CVE-2023-22618/index.md)
```

## Sources

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

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