# CVE-2015-8225: Denial of service in n/a

> Remote attackers can crash Huawei smartphones via a crafted application exploiting the JPU driver, requiring system or camera permissions.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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:** No
- **Published:** 8 Jan 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hr43-w9f9-9mhh

## What is CVE-2015-8225?

CVE-2015-8225 is a medium-severity denial of service vulnerability in n/a, published on 8 Jan 2016. 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

The Joint Photographic Experts Group Processing Unit (JPU) driver in Huawei ALE smartphones with software before ALE-UL00C00B220 and ALE-TL00C01B220 and GEM-703L smartphones with software before V100R001C233B111 allows remote attackers to cause a denial of service (crash) via a crafted application with the system or camera permission, a different vulnerability than CVE-2015-8226.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2015-8225?

It affects 2 products.


Products: Huawei Ale Firmware, Huawei Gem-703l Firmware.

## How do I fix CVE-2015-8225?

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

## Is CVE-2015-8225 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-8226](https://insights.sbomify.com/CVE-2015-8226/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8225 and fix it if it is affected.

What it is: CVE-2015-8225 is a medium-severity denial of service vulnerability in n/a, published on 8 Jan 2016. 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-2015-8225 in the wild and no public exploit code.

Affected product: n/a. 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-2015-8225/ (Markdown: https://insights.sbomify.com/CVE-2015-8225/index.md)
```

## Sources

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

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