dbcve.org
OrvcApplication · Snapone

CVE-2023-25183

HIGH · 7.2 CVSS v3.1 Published 2023-05-22
Fix available
A fix is available. Upgrade to 7.3.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
In Snap One OvrC Pro versions prior to 7.2, when logged into the superuser account, a new functionality appears that could allow users to execute arbitrary commands on the hub device.

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 versions prior to 7.2 contain an authenticated command injection vulnerability accessible through the superuser account. The vulnerability stems from insufficient input sanitization in a feature exposed to superuser users, allowing execution of arbitrary operating system commands on the hub device.

MitigationUpgrade OvrC Pro to version 7.2 or later to remediate this vulnerability. If immediate patching is not feasible, restrict superuser account access and monitor for suspicious command execution activity.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 OvrC Pro version
    Access the OvrC Pro administrative interface or check the hub device system information to locate the currently installed software version number
    Affected if The displayed version is below 7.3.0 (for example, 7.2.x, 7.1.x, or earlier)
  2. Confirm superuser account presence
    Log into the OvrC Pro management console and navigate to user accounts or access control settings to verify if a superuser account is configured or active
    Affected if A superuser account exists and is enabled on the system
  3. Check for superuser-accessible features
    Review the OvrC Pro administrative panel for features that accept user input and are accessible to superuser accounts, such as network diagnostics, system utilities, or configuration tools
    Affected if Any feature accepting input is exposed to superuser accounts without visible input sanitization controls
  4. Audit for suspicious command execution
    Examine system logs, command history, or audit trails on the OvrC hub device for unexpected or unauthorized shell commands, script executions, or unusual system calls
    Affected if Logs show OS commands or scripts that were not initiated by legitimate administrative tasks

You are affected if your OvrC Pro version is below 7.3.0 and a superuser account with access to input-accepting features exists on the system.

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

Upgrade OvrC Pro to version 7.2 or later to remediate this vulnerability. If immediate patching is not feasible, restrict superuser account access and monitor for suspicious command execution activity.

Recommended fix Moderate confidence

OvrC Pro version 7.3.0 or later

  1. 1. Identify all OvrC Pro hub devices running versions prior to 7.3.0
  2. 2. Log into the OvrC Pro administrative interface
  3. 3. Navigate to the system settings or firmware update section
  4. 4. Check the current firmware version of each hub device
  5. 5. Initiate a firmware update to version 7.3.0 or later
  6. 6. Verify the update was successful by confirming the new version number
  7. 7. After updating, verify that the superuser account no longer has access to the hidden command execution functionality

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

Fix this in Orvc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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