# CVE-2024-50381: Missing Authentication for Critical Function in Snap One OVRC cloud

> Attackers can impersonate Hub devices to claim or unclaim devices using only MAC addresses, bypassing authentication in Snap One OVRC cloud.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Dec 2024
- **Updated:** 2 Dec 2024
- **Also known as:** GHSA-rgfw-9xmc-3h72

## What is CVE-2024-50381?

CVE-2024-50381 is a high-severity missing authorization vulnerability in Snap One OVRC cloud, published on 2 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability exists in Snap One OVRC cloud where an attacker can impersonate a Hub device and send requests to claim and unclaim devices. The attacker only needs to provide the MAC address of the targeted device and can make a request to unclaim it from its original connection and make a request to claim it.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2024-50381?


## How do I fix CVE-2024-50381?

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

## Is CVE-2024-50381 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50381 and fix it if it is affected.

What it is: CVE-2024-50381 is a high-severity missing authorization vulnerability in Snap One OVRC cloud, published on 2 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-50381 in the wild and no public exploit code.

Affected product: Snap One OVRC cloud. 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-2024-50381/ (Markdown: https://insights.sbomify.com/CVE-2024-50381/index.md)
```

## Sources

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

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