# CVE-2016-1495: Integer overflow in n/a

> Attackers can cause system crashes or gain privileges via a crafted application exploiting an integer overflow in Huawei Mate S graphics drivers.

- **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:** No
- **Published:** 13 Apr 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vcf7-g5m7-j63w

## What is CVE-2016-1495?

CVE-2016-1495 is a high-severity vulnerability in n/a, published on 13 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

Integer overflow in the graphics drivers in Huawei Mate S smartphones with software CRR-TL00 before CRR-TL00C01B160SP01, CRR-UL00 before CRR-UL00C00B160, and CRR-CL00 before CRR-CL00C92B161 allows attackers to cause a denial of service (system crash) or gain privileges via a crafted application, which triggers a heap-based buffer overflow.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2016-1495?

It affects 1 product.


Products: Huawei Mate S Firmware.

## How do I fix CVE-2016-1495?

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

## Is CVE-2016-1495 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-8307](https://insights.sbomify.com/CVE-2015-8307/): Privilege escalation in n/a (high 7.8)
- [CVE-2015-8318](https://insights.sbomify.com/CVE-2015-8318/): Memory corruption in n/a (high 7.8)
- [CVE-2015-8319](https://insights.sbomify.com/CVE-2015-8319/): Memory corruption in n/a (high 7.8)
- [CVE-2015-8680](https://insights.sbomify.com/CVE-2015-8680/): Privilege escalation in n/a (high 7.8)
- [CVE-2015-8681](https://insights.sbomify.com/CVE-2015-8681/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1495 and fix it if it is affected.

What it is: CVE-2016-1495 is a high-severity vulnerability in n/a, published on 13 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-2016-1495 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-2016-1495/ (Markdown: https://insights.sbomify.com/CVE-2016-1495/index.md)
```

## Sources

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

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