Authenticated code execution via malicious update packages
Published Jul 28, 2022 · Updated Apr 17, 2025
Code injection in Ovarro TBox firmware 1.44 and earlier allows remote authenticated users to execute malicious code via update packages. The proprietary Modbus update functions accept an attacker-supplied IPK configuration package, then extract, install, and execute it without enforcing a trusted signature. The package-update path is required; with user protection enabled, exploitation requires the highest access level and a race with a legitimate update.
Summary
What happened
Code injection in Ovarro TBox firmware 1.44 and earlier allows remote authenticated users to execute malicious code via update packages. The proprietary Modbus update functions accept an attacker-supplied IPK configuration package, then extract, install, and execute it without enforcing a trusted signature. The package-update path is required; with user protection enabled, exploitation requires the highest access level and a race with a legitimate update.
The record
- CVE
- CVE-2021-22646
- Published
- Jul 28, 2022
- Updated
- Apr 17, 2025
- Vendor
- Ovarro
- Product
- TBox
- Classifications
- CWE-94, T0866
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 28, 2022CVE publishedPublication date reported by the CVE source.
- Apr 17, 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=LT2
- Affected versionversion=MS-CPU32
- Affected versionversion=MS-CPU32-S2
- Affected versionversion=RM2
- Affected versionversion=TG2
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