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

> Attackers can cause a system panic and denial of service on Huawei Sophia-L10 smartphones by installing a crafted application with specific privileges.

- **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:** 7 Apr 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jrr2-6pgv-vqqm

## What is CVE-2015-8305?

CVE-2015-8305 is a medium-severity denial of service vulnerability in n/a, published on 7 Apr 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

Huawei Sophia-L10 smartphones with software before P7-L10C900B852 allow attackers to cause a denial of service (system panic) via a crafted application with the system or camera privilege.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Huawei P7 Firmware.

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

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

## Is CVE-2015-8305 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-8304](https://insights.sbomify.com/CVE-2015-8304/): Integer overflow in n/a (high 7.8)
- [CVE-2015-7740](https://insights.sbomify.com/CVE-2015-7740/): Denial of service in n/a (medium 5.5)
- [CVE-2015-8223](https://insights.sbomify.com/CVE-2015-8223/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-8305 is a medium-severity denial of service vulnerability in n/a, published on 7 Apr 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-8305 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-8305/ (Markdown: https://insights.sbomify.com/CVE-2015-8305/index.md)
```

## Sources

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

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