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.

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.

In Snap One OVRC cloud platform, the Hub is a device that is used to centralize and manage nested devices connected to it. A vulnerability exists where an attacker can impersonate a hub and send device requests to claim already claimed devices. The OVRC cloud platform receives the requests but does not validate if the found devices are already managed by another user. When supplying Snap One OVRC cloud servers with a random MAC address, it will return information about the device. The MAC address of devices can be enumerated in an attack and their information will be disclosed by the OVRC cloud. Snap One OVRC cloud servers contain a route that can be exploited where an attacker can use to bypass requirements and claim devices outright. Snap One OvrC Pro versions prior to 7.3 utilize HTTP connections when downloading a program from their servers. Because it does not use HTTPS, OVRC Pro devices are susceptible to exploitation. 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 and lack of firmware signature could allow attackers to upload arbitrary firmware updates resulting in code execution. Devices using Snap One OVRC cloud are sent to web address when accessing a web management interface utilizing a HTTP connection. It is possible for attackers to impersonate a device and supply malicious…