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

> Local attackers can gain root access via the UART port on Mediatrix 4102 devices, requiring physical access to exploit.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 17 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-hrv9-f2qw-v2xg

## What is CVE-2022-43096?

CVE-2022-43096 is a medium-severity vulnerability in n/a, published on 17 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Mediatrix 4102 before v48.5.2718 allows local attackers to gain root access via the UART port.

Weakness: CWE-1191 (On-Chip Debug and Test Interface With Improper Access Control)

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

It affects 1 product.


Products: M5t Mediatrix 4102s Firmware.

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

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

## Is CVE-2022-43096 being exploited?

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

Public exploit code:

- https://github.com/ProxyStaffy/Mediatrix-CVE-2022-43096 (github_poc): https://github.com/ProxyStaffy/Mediatrix-CVE-2022-43096

## Fix prompt for AI coding agents

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

What it is: CVE-2022-43096 is a medium-severity vulnerability in n/a, published on 17 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43096 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-2022-43096/ (Markdown: https://insights.sbomify.com/CVE-2022-43096/index.md)
```

## Sources

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

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