Filtered by vendor Motorola
Subscriptions
Total
97 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2022-30271 | 1 Motorola | 2 Ace1000, Ace1000 Firmware | 2024-08-03 | 9.8 Critical |
The Motorola ACE1000 RTU through 2022-05-02 ships with a hardcoded SSH private key and initialization scripts (such as /etc/init.d/sshd_service) only generate a new key if no private-key file exists. Thus, this hardcoded key is likely to be used by default. | ||||
CVE-2022-30274 | 1 Motorola | 2 Ace1000, Ace1000 Firmware | 2024-08-03 | 9.8 Critical |
The Motorola ACE1000 RTU through 2022-05-02 uses ECB encryption unsafely. It can communicate with an XRT LAN-to-radio gateway by means of an embedded client. Credentials for accessing this gateway are stored after being encrypted with the Tiny Encryption Algorithm (TEA) in ECB mode using a hardcoded key. Similarly, the ACE1000 RTU can route MDLC traffic over Extended Command and Management Protocol (XCMP) and Network Layer (XNL) networks via the MDLC driver. Authentication to the XNL port is protected by TEA in ECB mode using a hardcoded key. | ||||
CVE-2022-30270 | 1 Motorola | 2 Ace1000, Ace1000 Firmware | 2024-08-03 | 9.8 Critical |
The Motorola ACE1000 RTU through 2022-05-02 has default credentials. It exposes an SSH interface on port 22/TCP. This interface is used for remote maintenance and for SFTP file-transfer operations that are part of engineering software functionality. Access to this interface is controlled by 5 preconfigured accounts (root, abuilder, acelogin, cappl, ace), all of which come with default credentials. Although the ACE1000 documentation mentions the root, abuilder and acelogin accounts and instructs users to change the default credentials, the cappl and ace accounts remain undocumented and thus are unlikely to have their credentials changed. | ||||
CVE-2022-30272 | 1 Motorola | 2 Ace1000, Ace1000 Firmware | 2024-08-03 | 7.2 High |
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. | ||||
CVE-2022-27813 | 1 Motorola | 4 Mtm5400, Mtm5400 Firmware, Mtm5500 and 1 more | 2024-08-03 | 8.1 High |
Motorola MTM5000 series firmwares lack properly configured memory protection of pages shared between the OMAP-L138 ARM and DSP cores. The SoC provides two memory protection units, MPU1 and MPU2, to enforce the trust boundary between the two cores. Since both units are left unconfigured by the firmwares, an adversary with control over either core can trivially gain code execution on the other, by overwriting code located in shared RAM or DDR2 memory regions. | ||||
CVE-2022-26942 | 1 Motorola | 4 Mtm5400, Mtm5400 Firmware, Mtm5500 and 1 more | 2024-08-03 | 8.2 High |
The Motorola MTM5000 series firmwares lack pointer validation on arguments passed to trusted execution environment (TEE) modules. Two modules are used, one responsible for KVL key management and the other for TETRA cryptographic functionality. In both modules, an adversary with non-secure supervisor level code execution can exploit the issue in order to gain secure supervisor code execution within the TEE. This constitutes a full break of the TEE module, exposing the device key as well as any TETRA cryptographic keys and the confidential TETRA cryptographic primitives. | ||||
CVE-2022-26943 | 1 Motorola | 4 Mtm5400, Mtm5400 Firmware, Mtm5500 and 1 more | 2024-08-03 | 8.8 High |
The Motorola MTM5000 series firmwares generate TETRA authentication challenges using a PRNG using a tick count register as its sole entropy source. Low boottime entropy and limited re-seeding of the pool renders the authentication challenge vulnerable to two attacks. First, due to the limited boottime pool entropy, an adversary can derive the contents of the entropy pool by an exhaustive search of possible values, based on an observed authentication challenge. Second, an adversary can use knowledge of the entropy pool to predict authentication challenges. As such, the unit is vulnerable to CVE-2022-24400. | ||||
CVE-2022-3917 | 1 Motorola | 2 Moto E20, Moto E20 Firmware | 2024-08-03 | 4.6 Medium |
Improper access control of bootloader function was discovered in Motorola Mobility Motorola e20 prior to version RONS31.267-38-8 allows attacker with local access to read partition or RAM data. | ||||
CVE-2023-31531 | 1 Motorola | 2 Cx2l, Cx2l Firmware | 2024-08-02 | 8.8 High |
Motorola CX2L Router 1.0.1 was discovered to contain a command injection vulnerability via the tomography_ping_number parameter. | ||||
CVE-2023-31529 | 1 Motorola | 2 Cx2l, Cx2l Firmware | 2024-08-02 | 8.8 High |
Motorola CX2L Router 1.0.1 was discovered to contain a command injection vulnerability via the system_time_timezone parameter. | ||||
CVE-2023-31530 | 1 Motorola | 2 Cx2l, Cx2l Firmware | 2024-08-02 | 8.8 High |
Motorola CX2L Router 1.0.1 was discovered to contain a command injection vulnerability via the smartqos_priority_devices parameter. | ||||
CVE-2023-31528 | 1 Motorola | 2 Cx2l, Cx2l Firmware | 2024-08-02 | 8.8 High |
Motorola CX2L Router 1.0.1 was discovered to contain a command injection vulnerability via the staticroute_list parameter. | ||||
CVE-2024-23627 | 1 Motorola | 2 Mr2600, Mr2600 Firmware | 2024-08-01 | 9 Critical |
A command injection vulnerability exists in the 'SaveStaticRouteIPv4Params' parameter of the Motorola MR2600. A remote attacker can exploit this vulnerability to achieve command execution. Authentication is required, however can be bypassed. | ||||
CVE-2024-23630 | 1 Motorola | 2 Mr2600, Mr2600 Firmware | 2024-08-01 | 9 Critical |
An arbitrary firmware upload vulnerability exists in the Motorola MR2600. An attacker can exploit this vulnerability to achieve code execution on the device. Authentication is required, however can be bypassed. | ||||
CVE-1999-0919 | 1 Motorola | 1 Motorola Cablerouter | 2024-08-01 | N/A |
A memory leak in a Motorola CableRouter allows remote attackers to conduct a denial of service via a large number of telnet connections. | ||||
CVE-1999-0816 | 1 Motorola | 1 Motorola Cablerouter | 2024-08-01 | N/A |
The Motorola CableRouter allows any remote user to connect to and configure the router on port 1024. | ||||
CVE-2022-4001 | 1 Motorola | 1 Q14 Mesh Router Firmware | 2024-08-01 | 7.3 High |
An authentication bypass vulnerability could allow an attacker to access API functions without authentication. |