Approved changes feed: RSS · Atom

cpe:2.3:h:snapone:pakedge_rk-1:-:*:*:*:*:*:*:*

part: h version: - update: *

VendorSnapone (ee6d010a-18df-5253-865c-3fac2e7344c1)
ProductPakedge Rk 1 (cf450c30-671b-51fb-9cfe-1c0e9b5ce423)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-31245 not_vulnerable 2026-06-08 06:04:42.431734 Details available
HIGH (7.1)
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.
Published: 2023-05-22T19:37:10.365Z
Updated: 2025-01-16T21:33:28.000Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-31241 not_vulnerable 2026-06-08 06:04:42.422747 Details available
HIGH (8.6)
Snap One OvrC cloud servers contain a route an attacker can use to bypass requirements and claim devices outright.
Published: 2023-05-22T19:26:22.401Z
Updated: 2025-01-16T21:33:49.710Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-28412 not_vulnerable 2026-06-08 06:01:10.702008 Details available
MEDIUM (5.3)
When supplied with a random MAC address, Snap One OvrC cloud servers will return information about the device. The MAC address of devices can be enumerated in an attack and the OvrC cloud will disclose their information.
Published: 2023-05-22T19:24:06.082Z
Updated: 2025-01-16T21:33:55.805Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-28386 not_vulnerable 2026-06-08 06:01:10.627200 Details available
HIGH (8.6)
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.
Published: 2023-05-22T19:35:12.357Z
Updated: 2025-01-16T21:33:35.168Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.