dbcve.org
OrvcApplication · Snapone

CVE-2023-28386

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-22
Fix available
A fix is available. Upgrade to 7.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Snap One OvrC Pro devices versions 7.2 and prior do not validate firmware updates correctly. The device only calculates the MD5 hash of the firmware and does not check using a private-public key mechanism. The lack of complete PKI system firmware signature could allow attackers to upload arbitrary firmware updates, resulting in code execution.

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

Snap One OvrC Pro devices versions 7.2 and prior only verify firmware integrity using MD5 hash calculation, lacking proper cryptographic signature verification via PKI. Attackers can craft malicious firmware with a matching MD5 hash and upload it to achieve arbitrary code execution on the device.

MitigationImplement proper PKI-based digital signature verification requiring firmware to be signed with a private key and validated against the corresponding public key stored on the device before execution. Until a patch is available, isolate affected devices on restricted networks and avoid processing untrusted firmware files.

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
High
Integrity
High
Availability
High

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

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 the device model
    Log into the OvrC Pro web interface or check the device label to confirm it is a Snap One OvrC Pro or OvrC-enabled device. Note the exact model name.
    Affected if The device is not a Snap One OvrC or OvrC Pro product - this CVE only affects those specific devices.
  2. Determine the firmware version
    In the OvrC Pro web interface, navigate to Settings or System Info to view the current firmware version. Alternatively, check via the OvrC mobile app under device details.
    Affected if The firmware version is 7.2 or prior (versions less than 7.3.0 are affected).
  3. Verify the firmware update mechanism
    Attempt to access the firmware update section in the device web interface or check if the device accepts firmware files for manual updates. Note whether any signature validation prompts or errors appear during the process.
    Affected if The device accepts firmware updates without requiring cryptographic signature validation - this indicates the vulnerable MD5-only verification is in use.
  4. Check for PKI signature verification
    Review device logs or firmware update responses to determine if the device validates firmware using PKI-based digital signatures. If the device only reports MD5 or hash mismatches without signature validation, the vulnerability is present.
    Affected if The device only checks MD5 hashes for firmware integrity and does not perform PKI signature verification - this confirms the vulnerability.

The device is affected if it is a Snap One OvrC Pro running firmware version 7.2 or prior, and the firmware update process relies solely on MD5 hash verification instead of PKI-based cryptographic signature validation.

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 PKI-based digital signature verification requiring firmware to be signed with a private key and validated against the corresponding public key stored on the device before execution. Until a patch is available, isolate affected devices on restricted networks and avoid processing untrusted firmware files.

Recommended fix High confidence

Firmware version 7.3.0

  1. 1. Identify the specific OvrC Pro device model in use
  2. 2. Check the current firmware version through the device management interface or control panel
  3. 3. Navigate to the firmware update section in the OvrC Pro web interface or mobile app
  4. 4. Download and apply firmware version 7.3.0 or later from the official Control4/Snap One support resources
  5. 5. Verify the firmware upgrade was successful by confirming the new version in the device settings
  6. 6. After upgrade, verify that firmware updates now require proper cryptographic signature validation

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

Fix this in Orvc Scoped from the published advisory
  • Consultation12.0 h
  • Implementation80.0 h
  • Testing32.0 h
  • Review / QA20.0 h
144.0 hours of engineering $25,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 $40,320.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28386 — 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-28386 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