dbcve.org
OrvcApplication · Snapone

CVE-2023-31245

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

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
Devices using Snap One OvrC cloud are sent to a web address when accessing a web management interface using a HTTP connection. Attackers could impersonate a device and supply malicious information about the device’s web server interface. By supplying malicious parameters, an attacker could redirect the user to arbitrary and dangerous locations on the web.

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 cloud devices redirect users to a web address when accessing the web management interface over HTTP. An attacker can impersonate a device and supply malicious parameters in the redirect, allowing redirection of users to arbitrary and dangerous external websites—this is an open redirect vulnerability.

MitigationImplement strict allowlist-based validation of redirect URLs on the server side, replace HTTP with HTTPS for all management interface connections, and reject any redirect parameters containing untrusted or external domains.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Snap One OvrC device in your environment
    Locate Snap One OvrC cloud-enabled devices on your network. Check device documentation, network scans, or management interfaces for 'OvrC' or 'Snap One' branding.
    Affected if A Snap One OvrC device exists in your environment.
  2. Check installed firmware version
    Access the device web management interface or use the OvrC mobile/cloud app to view the firmware version. Compare against version 7.3.0.
    Affected if The installed version is less than 7.3.0.
  3. Verify if HTTP access is enabled
    Attempt to access the device web management interface using HTTP (not HTTPS). Check the device configuration settings for HTTP/HTTPS access options.
    Affected if HTTP access is enabled and the management interface responds over HTTP.
  4. Inspect redirect behavior
    If HTTP access is available, observe any redirect behavior when accessing the interface. Note if redirect parameters appear in the URL after initial access.
    Affected if The device performs URL redirects and exposes redirect parameters in the request.
  5. Check for external domain redirects
    If redirect functionality is observable, test whether the redirect parameter accepts external domains by examining URL patterns or reviewing proxy/server logs for outgoing redirects.
    Affected if The redirect functionality allows or has allowed redirection to external/untrusted domains.

A Snap One OvrC device running firmware version below 7.3.0 with HTTP access enabled is vulnerable to open redirect attacks via the web management interface.

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 strict allowlist-based validation of redirect URLs on the server side, replace HTTP with HTTPS for all management interface connections, and reject any redirect parameters containing untrusted or external domains.

Recommended fix Moderate confidence

Orvc version 7.3.0 or later

  1. 1. Identify all Orvc devices in the environment running versions prior to 7.3.0
  2. 2. Consult the official Control4/Snap One documentation for the upgrade procedure specific to your device model
  3. 3. Backup current device configurations before initiating the upgrade
  4. 4. Perform the upgrade to version 7.3.0 or later following vendor-provided instructions
  5. 5. Verify the upgrade was successful and confirm the new version number
  6. 6. Test the web management interface to confirm the open redirect vulnerability is remediated

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

Fix this in Orvc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
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,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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