# CVE-2017-17158: Information disclosure in Berlin-L21HN; Prague-AL00A; Prague-AL00B; Prague-AL00C; Prague-L31; Prague-TL00A; Prague-TL10A

> An attacker can expose sensitive information by sending crafted messages when a Huawei smartphone connects to a malicious charging device.

- **Severity:** Medium 4.6 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v5q8-jp9h-qfqv

## What is CVE-2017-17158?

CVE-2017-17158 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. Berlin-L21HN; Prague-AL00A; Prague-AL00B; Prague-AL00C; Prague-L31; Prague-TL00A; Prague-TL10A, published on 24 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Some Huawei smart phones with the versions before Berlin-L21HNC185B381; the versions before Prague-AL00AC00B223; the versions before Prague-AL00BC00B223; the versions before Prague-AL00CC00B223; the versions before Prague-L31C432B208; the versions before Prague-TL00AC01B223; the versions before Prague-TL00AC01B223 have an information exposure vulnerability. When the user's smart phone connects to the malicious device for charging, an unauthenticated attacker may activate some specific function by sending some specially crafted messages. Due to insufficient input validation of the messages, successful exploit may cause information exposure.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 7 products.


Products: Huawei Berlin-L21hn Firmware, Huawei Prague-Al00a Firmware, Huawei Prague-Al00b Firmware, Huawei Prague-Al00c Firmware, Huawei Prague-L31 Firmware, Huawei Prague-Tl00a Firmware, Huawei Prague-Tl10a Firmware.

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

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

## Is CVE-2017-17158 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17158 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. Berlin-L21HN; Prague-AL00A; Prague-AL00B; Prague-AL00C; Prague-L31; Prague-TL00A; Prague-TL10A, published on 24 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-17158 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. Berlin-L21HN; Prague-AL00A; Prague-AL00B; Prague-AL00C; Prague-L31; Prague-TL00A; Prague-TL10A. 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-17158/ (Markdown: https://insights.sbomify.com/CVE-2017-17158/index.md)
```

## Sources

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

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