CVE-2022-30274 json
The Motorola ACE1000 RTU through 2022-05-02 uses ECB encryption unsafely.
published 2022-07-26 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-52229
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
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.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-22-179-06 updated cvss 7.5
Motorola Solutions ACE1000
-
Motorola Solutions ACE1000affected: mitigation “While individual remediation steps are specified, note all vulnerabilities listed above can be resolved by upgrading the ACE1000 to MC-EDGE intelligent RTU.” motorolasolutions.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
forescout.com
/blog/
not-applicable
-
cisa.gov
/uscert/ics/advisories/icsa-22-179-06
mitigation, third-party-advisory, us-government-resource
Sources
- CVE List CVE-2022-30274
- NVD CVE-2022-30274
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.