First published: Tue Jul 26 2022(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Motorola Ace1000 Firmware | ||
Motorola ACE1000 | ||
All of | ||
Motorola Ace1000 Firmware | ||
Motorola ACE1000 | ||
Motorola Solutions ACE1000 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for the Motorola ACE1000 RTU firmware mishandling is CVE-2022-30272.
CVE-2022-30272 has a severity rating of 7.2 (high).
CVE-2022-30272 affects the Motorola Ace1000 Firmware by mishandling firmware integrity.
Firmware updates in the Motorola ACE1000 RTU are performed either through the STS software suite or ACE1000 Easy Configurator.
The Common Weakness Enumeration (CWE) ID for CVE-2022-30272 is CWE-345.