Motorola MTM5000 Trusted Execution Environment key management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Motorola MTM5000. This vulnerability affects unknown code of the component Trusted Execution Environment. The manipulation leads to key management. This vulnerability is uniquely identified as CVE-2022-26942. Local access is required to approach this attack. No exploit exists. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in Motorola MTM5000 (version now known). It has been rated as critical. This issue affects some unknown processing of the component Trusted Execution Environment. The manipulation with an unknown input leads to a key management vulnerability. Using CWE to declare the problem leads to CWE-320. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was disclosed 10/19/2023. The identification of this vulnerability is CVE-2022-26942 since 03/11/2022. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.7
VulDB Temp Score: 6.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.2
CNA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Key managementCWE: CWE-320
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/11/2022 🔍10/19/2023 🔍
10/19/2023 🔍
10/19/2023 🔍
Sources
Status: Not definedCVE: CVE-2022-26942 (🔍)
GCVE (CVE): GCVE-0-2022-26942
GCVE (VulDB): GCVE-100-242927
Entry
Created: 10/19/2023 01:30 PMChanges: 10/19/2023 01:30 PM (44)
Complete: 🔍
Cache ID: 244:594:40
No comments yet. Languages: en.
Please log in to comment.