# CVE-2024-50380: Authentication Bypass by Spoofing in Snap One OVRC cloud

> Attackers can impersonate devices by spoofing MAC addresses to access sensitive information in Snap One OVRC cloud.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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-vgr3-gmw5-qgp2

## What is CVE-2024-50380?

CVE-2024-50380 is a high-severity authentication bypass 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

Snap One OVRC cloud uses the MAC address as an identifier to provide information when requested. An attacker can impersonate other devices by supplying enumerated MAC addresses and receive sensitive information about the device.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2024-50380 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-50380 is a high-severity authentication bypass 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-50380 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-50380/ (Markdown: https://insights.sbomify.com/CVE-2024-50380/index.md)
```

## Sources

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

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