# CVE-2023-21036: Other in Android

> A logic error in Android's BitmapExport.java fails to truncate images, potentially allowing unauthorized data access.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Mar 2023
- **Updated:** 25 Feb 2025
- **Also known as:** A-264261868, GHSA-c4q4-j9gc-fpq4, PUB-A-264261868

## What is CVE-2023-21036?

CVE-2023-21036 is a medium-severity vulnerability in Google Android, published on 24 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In BitmapExport.java, there is a possible failure to truncate images due to a logic error in the code.Product: AndroidVersions: Android kernelAndroid ID: A-264261868References: N/A

Weakness: CWE-703 (Improper Check or Handling of Exceptional Conditions)

## Which versions are affected by CVE-2023-21036?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2023-21036?

Apply the vendor's patch.

## Is CVE-2023-21036 being exploited?

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

Public exploit code:

- Detection and sanitization for Acropalypse Now - CVE-2023-21036 (github_poc): https://github.com/infobyte/CVE-2023-21036
- Discord bot for mitigating the aCropalypse vulnerability (CVE-2023-21036, CVE-2023-28303) by retroactively deleting vulnerable images (github_poc): https://github.com/qixils/AntiCropalypse
- Web tool for detecting Acropalypse (CVE-2023-21036) https://lordofpipes.github.io/acropadetect/ (github_poc): https://github.com/lordofpipes/acropadetect
- CVE-2023-21036 detection in Go (github_poc): https://github.com/notaSWE/gocropalypse
- A lightweight CLI tool to detect and reconstruct cropped images vulnerable to Acropalypse (CVE-2023-21036 and CVE-2023-28303) written in Python. (github_poc): https://github.com/iqbaalilmii/acropalypse-reconstructor
- X-Ways Acropalypse extension detects CVE-2023-21036 in common images  (github_poc): https://github.com/PolitoInc/XWFAcropalypse

## 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-2023-21036 and fix it if it is affected.

What it is: CVE-2023-21036 is a medium-severity vulnerability in Google Android, published on 24 Mar 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-2023-21036 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-2023-21036/ (Markdown: https://insights.sbomify.com/CVE-2023-21036/index.md)
```

## Sources

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

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