Skip to content

Vendor

Snap One, LLC vulnerabilities

15 published CVES affecting Snap One, LLC, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
15
Critical
6
High
6
Medium
3
Low
0
Unscored
0
CISA KEV
0
Atom feed of Snap One, LLC alerts

Products

Latest Snap One, LLC CVEs

Newest publication first

  1. CriticalCVSS 9.2 EPSS 0.43%

    Snap One WattBox 800 and 820 series firmware versions prior to 2.10.0.0 contain undisclosed diagnostic HTTP endpoints that require only the device MAC address and service tag for authentication, both of which are printed in plaintext on the physical device label. Attackers with a...

  2. MediumCVSS 6.1 EPSS 0.39%

    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 atta...

  3. CriticalCVSS 9.8 EPSS 0.42%

    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 t...

  4. HighCVSS 7.5 EPSS 0.52%

    The Hub in the Snap One OvrC cloud platform is a device used to centralize and manage nested devices connected to it. A vulnerability exists in which an attacker could impersonate a hub and send device requests to claim already claimed devices. The OvrC cloud platform receives th...

  5. HighCVSS 7.8 EPSS 0.12%

    Snap One Wattbox WB-300-IP-3 versions WB10.9a17 and prior use a proprietary local area network (LAN) protocol that does not verify updates to the device. An attacker could upload a malformed update file to the device and execute arbitrary code.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.