# CVE-2022-28866: Missing authorization in n/a

> Attackers can bypass authentication to view sensitive data and modify system configurations, potentially causing denial of service on Nokia AirFrame BMC devices.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cq2f-p9qc-xc92

## What is CVE-2022-28866?

CVE-2022-28866 is a high-severity missing authorization vulnerability in n/a, published on 11 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple Improper Access Control was discovered in Nokia AirFrame BMC Web GUI < R18 Firmware v4.13.00. It does not properly validate requests for access to (or editing of) data and functionality in all endpoints under /#settings/* and /api/settings/*. By not verifying the permissions for access to resources, it allows a potential attacker to view pages, with sensitive data, that are not allowed, and modify system configurations also causing DoS, which should be accessed only by user with administration profile, bypassing all controls (without checking for user identity).

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2022-28866?

It affects 1 product.


Products: Nokia Airframe Bmc Web Gui R18 Firmware.

## How do I fix CVE-2022-28866?

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

## Is CVE-2022-28866 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-28866 and fix it if it is affected.

What it is: CVE-2022-28866 is a high-severity missing authorization vulnerability in n/a, published on 11 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-28866 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-2022-28866/ (Markdown: https://insights.sbomify.com/CVE-2022-28866/index.md)
```

## Sources

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

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