# CVE-2022-27813: Unconfigured memory protection modules in Motorola MTM5000

> Attackers with control over one core can execute code on the other due to unconfigured memory protection units in Motorola MTM5000 firmware.

- **Severity:** High 8.1 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:H/E:F/RL:U/RC:C/CR:X/IR:X/AR:X/MAV:L/MAC:L/MPR:H/MUI:N/MS:C/MC:L/MI:H/MA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-m8m2-8cm8-p8jv

## What is CVE-2022-27813?

CVE-2022-27813 is a high-severity vulnerability in Motorola Mobile Radio, published on 19 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-1260 (Improper Handling of Overlap Between Protected Memory Ranges)

## Which versions are affected by CVE-2022-27813?

It affects 2 products.


Products: Motorola Mtm5400 Firmware, Motorola Mtm5500 Firmware.

## How do I fix CVE-2022-27813?

No fix has been published for CVE-2022-27813 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-27813 being exploited?

There is no known exploitation of CVE-2022-27813 in the wild and no public exploit code.

## Other vulnerabilities in Motorola Mobile Radio

- [CVE-2022-26941](https://insights.sbomify.com/CVE-2022-26941/): Format string vulnerability in AT+CTGL command in Motorola MTM5000 (critical 9.6)
- [CVE-2022-26943](https://insights.sbomify.com/CVE-2022-26943/): Weak PRNG entropy source used for authentication challenge generation in Motorola MTM5000 (high 8.8)
- [CVE-2022-26942](https://insights.sbomify.com/CVE-2022-26942/): Multiple missing pointer validation checks in trusted execution module in Motorola MTM5000 (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-27813 and fix it if it is affected.

What it is: CVE-2022-27813 is a high-severity vulnerability in Motorola Mobile Radio, published on 19 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-27813 in the wild and no public exploit code.

Affected product: Motorola Mobile Radio. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-27813/ (Markdown: https://insights.sbomify.com/CVE-2022-27813/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-27813
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-27813
- OSV: https://osv.dev/vulnerability/CVE-2022-27813

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-27813/
Summaries are generated and may contain mistakes; the official description above is the record.