Motorola MTM5000 Core overlap between protected memory ranges

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.7$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Motorola MTM5000. Impacted is an unknown function of the component Core Handler. This manipulation causes an unknown weakness. The identification of this vulnerability is CVE-2022-27813. The attack can only be executed locally. There is no exploit available.

Detailsinfo

A vulnerability classified as critical was found in Motorola MTM5000 (affected version unknown). Affected by this vulnerability is an unknown functionality of the component Core Handler. The CWE definition for the vulnerability is CWE-1260. The product allows address regions to overlap, which can result in the bypassing of intended memory protection. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was shared 10/19/2023. This vulnerability is known as CVE-2022-27813 since 03/24/2022. Neither technical details nor an exploit are publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.7
VulDB Meta Temp Score: 7.7

VulDB Base Score: 6.7
VulDB Temp Score: 6.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.2
NVD Vector: 🔍

CNA Base Score: 8.1
CNA Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Improper handling of overlap between protected memory ranges
CWE: CWE-1260 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

03/24/2022 🔍
10/19/2023 +573 days 🔍
10/19/2023 +0 days 🔍
11/11/2023 +23 days 🔍

Sourcesinfo

Status: Not defined

CVE: CVE-2022-27813 (🔍)
GCVE (CVE): GCVE-0-2022-27813
GCVE (VulDB): GCVE-100-242929

Entryinfo

Created: 10/19/2023 13:31
Updated: 11/11/2023 12:12
Changes: 10/19/2023 13:31 (43), 11/11/2023 12:12 (12)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!