# CVE-2017-8178: Cross-site scripting in Vicky-AL00

> Remote attackers can execute arbitrary script code on Huawei smartphones by sending emails containing malicious code that triggers when viewed.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **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-4348-8467-8wg9

## What is CVE-2017-8178?

CVE-2017-8178 is a medium-severity cross-site scripting vulnerability in Huawei Technologies Co., Ltd. Vicky-AL00, published on 22 Nov 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Huawei Email APP Vicky-AL00 smartphones with software of earlier than VKY-AL00C00B171 versions has a stored cross-site scripting vulnerability. A remote attacker could exploit this vulnerability to send email that storing malicious code to a smartphone and waiting for a user to access this email that triggers execution of the code. An exploit could allow the attacker to execute arbitrary script code on the affected device.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Huawei Vicky-Al00 Firmware.

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

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

## Is CVE-2017-8178 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8178 is a medium-severity cross-site scripting vulnerability in Huawei Technologies Co., Ltd. Vicky-AL00, published on 22 Nov 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-8178 in the wild and no public exploit code.

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

## Sources

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

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