# CVE-2017-2733: Information disclosure in Honor 6X

> A malicious app can read the SIM card PIN ciphertext due to improper file permissions on Honor 6X devices.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mw53-3g7g-86j9

## What is CVE-2017-2733?

CVE-2017-2733 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. Honor 6X, 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

Honor 6X smartphones with software versions earlier than BLN-AL10C00B357 and versions earlier than BLN-AL20C00B357 have an information leak vulnerability due to improper file permission configuration. An attacker tricks a user into installing a malicious application on the smart phone, and the application can get the file that keep the cipher text of the SIM card PIN.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Huawei Honor 6x Firmware.

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

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

## Is CVE-2017-2733 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. Honor 6X

- [CVE-2017-2728](https://insights.sbomify.com/CVE-2017-2728/): Auth bypass in Honor 6X (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2733 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. Honor 6X, 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-2733 in the wild and no public exploit code.

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

## Sources

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

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