Device hijacking via unchecked hub ownership
Published May 22, 2023 · Updated Jan 16, 2025
Improper resource locking in Snap One OvrC before 7.3 allows remote attackers to claim managed devices by impersonating a hub. The cloud platform processes hub device-claim requests without checking whether another user already manages the discovered devices. No authentication or user interaction is required, and a successful request associates those devices with the impersonated hub.
Summary
What happened
Improper resource locking in Snap One OvrC before 7.3 allows remote attackers to claim managed devices by impersonating a hub. The cloud platform processes hub device-claim requests without checking whether another user already manages the discovered devices. No authentication or user interaction is required, and a successful request associates those devices with the impersonated hub.
The record
- CVE
- CVE-2023-28649
- Published
- May 22, 2023
- Updated
- Jan 16, 2025
- Vendor
- Snap One, LLC
- Product
- OvrC
- Classifications
- CWE-413, CWE-20, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 2023CVE publishedPublication date reported by the CVE source.
- Jan 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <7.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo