# CVE-2017-8160: Use after free in Vicky-AL00A,Vicky-AL00C,Vicky-TL00A,Victoria-AL00A,Victoria-TL00A

> A use-after-free vulnerability in Huawei smartphone drivers allows attackers to execute arbitrary code via a malicious application.

- **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:** 22 Nov 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-93qj-fvc7-c37j

## What is CVE-2017-8160?

CVE-2017-8160 is a high-severity use after free vulnerability in Huawei Technologies Co., Ltd. Vicky-AL00A,Vicky-AL00C,Vicky-TL00A,Victoria-AL00A,Victoria-TL00A, published on 22 Nov 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

The Madapt Driver of some Huawei smart phones with software Earlier than Vicky-AL00AC00B172 versions,Vicky-AL00CC768B122,Vicky-TL00AC01B167,Earlier than Victoria-AL00AC00B172 versions,Victoria-TL00AC00B123,Victoria-TL00AC01B167 has a use after free (UAF) vulnerability. An attacker can trick a user to install a malicious application which has a high privilege to exploit this vulnerability, Successful exploitation may cause arbitrary code execution.

Weakness: CWE-416 (Use After Free)

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

It affects 5 products.


Products: Huawei Vicky-Al00a Firmware, Huawei Vicky-Al00c Firmware, Huawei Vicky-Tl00a Firmware, Huawei Victoria-Al00a Firmware, Huawei Victoria-Tl00a Firmware.

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

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

## Is CVE-2017-8160 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. Vicky-AL00A,Vicky-AL00C,Vicky-TL00A,Victoria-AL00A,Victoria-TL00A

- [CVE-2017-15330](https://insights.sbomify.com/CVE-2017-15330/): Use after free in Vicky-AL00A (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8160 and fix it if it is affected.

What it is: CVE-2017-8160 is a high-severity use after free vulnerability in Huawei Technologies Co., Ltd. Vicky-AL00A,Vicky-AL00C,Vicky-TL00A,Victoria-AL00A,Victoria-TL00A, published on 22 Nov 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-8160 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. Vicky-AL00A,Vicky-AL00C,Vicky-TL00A,Victoria-AL00A,Victoria-TL00A. 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-8160/ (Markdown: https://insights.sbomify.com/CVE-2017-8160/index.md)
```

## Sources

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

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