The Motorola ACE1000 RTU through 2022-05-02 mishandles firmware integrity. It utilizes either the STS software suite or ACE1000 Easy Configurator for performing firmware updates. In case of the Easy Configurator, firmware updates are performed through access to the Web UI where file system, kernel, package, bundle, or application images can be installed. Firmware updates for the Front End Processor (FEP) module are performed via access to the SSH interface (22/TCP), where a .hex file image is transferred and a bootloader script invoked. File system, kernel, package, and bundle updates are supplied as RPM (RPM Package Manager) files while FEP updates are supplied as S-rec files. In all cases, firmware images were found to have no authentication (in the form of firmware signing) and only relied on insecure checksums for regular integrity checks.
References
Link | Resource |
---|---|
https://www.cisa.gov/uscert/ics/advisories/icsa-22-179-06 | Mitigation Third Party Advisory US Government Resource |
https://www.forescout.com/blog/ | Not Applicable |
Configurations
Configuration 1 (hide)
AND |
|
Information
Published : 2022-07-26 16:15
Updated : 2022-08-02 13:11
NVD link : CVE-2022-30272
Mitre link : CVE-2022-30272
JSON object : View
CWE
CWE-345
Insufficient Verification of Data Authenticity
Products Affected
motorola
- ace1000_firmware
- ace1000