# CVE-2022-3229: Missing authorization in Unified Remote

> An unauthenticated attacker can bypass authentication in the web interface to disable security controls and execute arbitrary code on the host.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2023
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-v2r7-frxx-fmq5

## What is CVE-2022-3229?

CVE-2022-3229 is a critical missing authorization vulnerability in Unified Remote, published on 6 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Because the web management interface for Unified Intents' Unified Remote solution does not itself require authentication, a remote, unauthenticated attacker can change or disable authentication requirements for the Unified Remote protocol, and leverage this now-unauthenticated access to run code of the attacker's choosing.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-285 (Improper Authorization)

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

It affects 1 product.


Products: Unifiedremote Unified Remote.

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

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

## Is CVE-2022-3229 being exploited?

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

Public exploit code:

- Unified Remote Auth Bypass to RCE (metasploit)

## Other vulnerabilities in Unified Remote

- [CVE-2023-52252](https://insights.sbomify.com/CVE-2023-52252/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3229 is a critical missing authorization vulnerability in Unified Remote, published on 6 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3229 exists.

Affected product: Unified Remote. 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-3229/ (Markdown: https://insights.sbomify.com/CVE-2022-3229/index.md)
```

## Sources

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

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