# CVE-2020-0470: Memory corruption in Android

> A heap buffer overflow in Android's restoration code allows remote attackers to disclose information via user interaction.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** A-166268541, ASB-A-166268541, GHSA-w837-6x9x-3ccv, SUSE-SU-2023:2314-1

## What is CVE-2020-0470?

CVE-2020-0470 is a medium-severity memory corruption vulnerability in Google Android, published on 14 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In extend_frame_highbd of restoration.c, there is a possible out of bounds write due to a heap buffer overflow. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-11 Android-10Android ID: A-166268541

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2020-0470?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libaom` | SUSE:Linux Enterprise Real Time 15 SP3 | All versions | 1.0.0-150200.3.15.1 |
| `libaom` | openSUSE:Leap 15.4 | All versions | 1.0.0-150200.3.15.1 |

Products: Google Android.

## How do I fix CVE-2020-0470?

Apply the vendor's patch.

## Is CVE-2020-0470 being exploited?

There is no known exploitation of CVE-2020-0470 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-2020-0470 and fix it if it is affected.

What it is: CVE-2020-0470 is a medium-severity memory corruption vulnerability in Google Android, published on 14 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-0470 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-2020-0470/ (Markdown: https://insights.sbomify.com/CVE-2020-0470/index.md)
```

## Sources

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

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