# CVE-2017-0663: Memory corruption in Android

> Remote attackers can execute arbitrary code in Android via a crafted file exploiting a memory corruption flaw in libxml2.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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 Jun 2017
- **Updated:** 14 Oct 2026
- **Also known as:** DEBIAN-CVE-2017-0663, ECHO-d74a-1a43-82c4, GHSA-9cf7-h7g3-cg3p, UBUNTU-CVE-2017-0663

## What is CVE-2017-0663?

CVE-2017-0663 is a high-severity memory corruption vulnerability in Google Android, published on 14 Jun 2017. 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

A remote code execution vulnerability in libxml2 could enable an attacker using a specially crafted file to execute arbitrary code within the context of an unprivileged process. This issue is rated as High due to the possibility of remote code execution in an application that uses this library. Product: Android. Versions: 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2. Android ID: A-37104170.

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

## Which versions are affected by CVE-2017-0663?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2017-0663?

Apply the vendor's patch.

## Is CVE-2017-0663 being exploited?

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

What it is: CVE-2017-0663 is a high-severity memory corruption vulnerability in Google Android, published on 14 Jun 2017. 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-2017-0663 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-2017-0663/ (Markdown: https://insights.sbomify.com/CVE-2017-0663/index.md)
```

## Sources

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

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