dbcve.org
OrvcApplication · Snapone

CVE-2023-28412

MEDIUM · 5.3 CVSS v3.1 Published 2023-05-22
Fix available
A fix is available. Upgrade to 7.3.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
When supplied with a random MAC address, Snap One OvrC cloud servers will return information about the device. The MAC address of devices can be enumerated in an attack and the OvrC cloud will disclose their information.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The OvrC cloud API discloses device information in response to arbitrary MAC address queries, allowing attackers to enumerate valid MAC addresses and harvest device details such as model, configuration, or ownership information.

MitigationImplement proper authentication and authorization checks before returning device information, and add rate limiting to prevent automated MAC address enumeration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OrvcApplication
Affected:< 7.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OvrC service presence
    Locate the Snapone Orvc installation by checking running services, installed applications, or network listeners on common ports (typically ports 80, 443, or 8080). Look for 'Orvc', 'OvrC', or 'Snapone' in service names or process lists.
    Affected if OvrC service is found running in the environment
  2. Determine installed Orvc version
    Check the installed version of Snapone Orvc by querying the service's about page, API endpoint (e.g., /api/version or /api/status), configuration files, or the application's web interface. Compare the version number against the affected range: versions prior to 7.3.0 are vulnerable.
    Affected if Installed version is lower than 7.3.0
  3. Verify API accessibility
    Confirm the OvrC cloud API is externally accessible by attempting to reach the API endpoint (typically at ovrccloud.com or a custom domain configured for the installation). Check network firewall rules and NAT configurations that allow inbound access to the OvrC service.
    Affected if The OvrC API is reachable from untrusted networks
  4. Test MAC enumeration vulnerability
    Send an HTTP GET request to the device info endpoint using a sample MAC address (format: XX:XX:XX:XX:XX:XX) without providing authentication credentials. Example: curl -s 'https://[ovrc-host]/api/device?mac=AA:BB:CC:DD:EE:FF'. Observe if the response returns device details such as model, configuration, or ownership information.
    Affected if API returns device information for arbitrary MAC addresses without requiring authentication

Environment is affected if Snapone Orvc version is below 7.3.0 AND the OvrC API is accessible and returns device details for unauthenticated MAC address queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.3.0 or later
Fixed in 7.3.0
Interim mitigation

Implement proper authentication and authorization checks before returning device information, and add rate limiting to prevent automated MAC address enumeration.

Recommended fix Moderate confidence

7.3.0

  1. Identify the Orvc device model and current firmware version
  2. Check Control4 or Snap One support resources for firmware 7.3.0 availability for your specific device
  3. Download firmware 7.3.0 or later from the official Control4 support site
  4. Follow the standard Control4/Orvc firmware update procedure, typically via the OvrC cloud portal or local controller interface
  5. After upgrade, verify the device is running version 7.3.0 or higher
  6. Test that the device no longer returns information when queried with random MAC addresses

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Orvc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28412 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28412 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data