# CVE-2018-21052: Memory corruption in n/a

> Incorrect shared memory usage in the vaultkeeper Trustlet allows arbitrary code execution on Samsung mobile devices with Exynos chipsets.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-94j2-cx6v-2wc5

## What is CVE-2018-21052?

CVE-2018-21052 is a critical memory corruption vulnerability in Google Android, published on 8 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Samsung mobile devices with N(7.x) and O(8.X) (Exynos chipsets) software. There is incorrect usage of shared memory in the vaultkeeper Trustlet, leading to arbitrary code execution. The Samsung ID is SVE-2018-12855 (October 2018).

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2018-21052?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2018-21052?

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

## Is CVE-2018-21052 being exploited?

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

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-21052 and fix it if it is affected.

What it is: CVE-2018-21052 is a critical memory corruption vulnerability in Google Android, published on 8 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-21052 in the wild and no public exploit code.

Affected product: Google Android. 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-2018-21052/ (Markdown: https://insights.sbomify.com/CVE-2018-21052/index.md)
```

## Sources

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

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