Unauthenticated code execution via unsigned firmware
Published May 22, 2023 · Updated Jan 16, 2025
Improper firmware integrity validation in Snap One OvrC Pro 7.2 and earlier allows remote attackers to execute code via firmware uploads. The update path calculates only an MD5 digest and accepts firmware without verifying a cryptographic signature against a trusted public key. No authentication or user interaction is required, and successful exploitation replaces trusted device firmware with attacker-controlled code.
Summary
What happened
Improper firmware integrity validation in Snap One OvrC Pro 7.2 and earlier allows remote attackers to execute code via firmware uploads. The update path calculates only an MD5 digest and accepts firmware without verifying a cryptographic signature against a trusted public key. No authentication or user interaction is required, and successful exploitation replaces trusted device firmware with attacker-controlled code.
The record
- CVE
- CVE-2023-28386
- Published
- May 22, 2023
- Updated
- Jan 16, 2025
- Vendor
- Snap One, LLC
- Product
- OvrC
- Classifications
- CWE-354, T1601.001
- 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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