# CVE-2022-45562: Privilege escalation in n/a

> Attackers with low-privilege backdoor access can escalate privileges to modify hardware settings and execute arbitrary commands on Omnia MPX Nodes.

- **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:** 2 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-5v2x-f677-rw5j

## What is CVE-2022-45562?

CVE-2022-45562 is a high-severity vulnerability in n/a, published on 2 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insecure permissions in Telos Alliance Omnia MPX Node v1.0.0 to v1.4.9 allow attackers to manipulate and access system settings with backdoor account low privilege, this can lead to change hardware settings and execute arbitrary commands in vulnerable system functions that is requires high privilege to access.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Telosalliance Omnia Mpx Node Firmware.

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

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

## Is CVE-2022-45562 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-43325](https://insights.sbomify.com/CVE-2022-43325/): Command injection in n/a (critical 9.8)
- [CVE-2022-36642](https://insights.sbomify.com/CVE-2022-36642/): Information disclosure in n/a (critical 9.8)
- [CVE-2022-43326](https://insights.sbomify.com/CVE-2022-43326/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45562 is a high-severity vulnerability in n/a, published on 2 Dec 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-45562 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-45562/ (Markdown: https://insights.sbomify.com/CVE-2022-45562/index.md)
```

## Sources

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

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