# CVE-2017-2735: Missing authorization in TIT-AL00

> A malicious app can exploit an exposed system interface to modify system properties on Huawei TIT-AL00 devices.

- **Severity:** High 7.1 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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-x63c-c6fq-2vvq

## What is CVE-2017-2735?

CVE-2017-2735 is a high-severity missing authorization vulnerability in Huawei Technologies Co., Ltd. TIT-AL00, 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

TIT-AL00 smartphones with software versions earlier before TIT-AL00C583B214 have a exposed system interface vulnerability. The software provides a system interface for interaction with external applications, but calling the interface is not properly restricted. An attacker could trick the user into installing a malicious application to call the interface and modify the system properties.

Weakness: CWE-749 (Exposed Dangerous Method or Function)

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

It affects 1 product.


Products: Huawei Y6 Pro Firmware.

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

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

## Is CVE-2017-2735 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2735 is a high-severity missing authorization vulnerability in Huawei Technologies Co., Ltd. TIT-AL00, 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-2735 in the wild and no public exploit code.

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

## Sources

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

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