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.
References
| Link | Resource |
|---|---|
| https://www.cisa.gov/news-events/ics-advisories/icsa-23-136-01 | Third Party Advisory US Government Resource |
| https://www.control4.com/docs/product/ovrc-software/release-notes/english/latest/ovrc-software-release-notes-rev-p.pdf | Release Notes |
| https://www.cisa.gov/news-events/ics-advisories/icsa-23-136-01 | Third Party Advisory US Government Resource |
| https://www.control4.com/docs/product/ovrc-software/release-notes/english/latest/ovrc-software-release-notes-rev-p.pdf | Release Notes |
Configurations
Configuration 1 (hide)
| AND |
|
History
09 Dec 2024, 18:15
| Type | Values Removed | Values Added |
|---|---|---|
| CWE | CWE-354 | |
| Summary | (en) 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. |
Information
Published : 2023-05-22 20:15
Updated : 2024-12-09 18:15
NVD link : CVE-2023-28386
Mitre link : CVE-2023-28386
CVE.ORG link : CVE-2023-28386
JSON object : View
Products Affected
control4
- ca-1
- ea-3
- ea-1
- ea-5
- ca-10
snapone
- orvc
- an-110-rt-2l1w
- pakedge_rt-3100
- pakedge_wr-1
- pakedge_rk-1
- an-110-rt-2l1w-wifi
- an-310-rt-4l2w
- ovrc-300-pro