# CVE-2018-9067: Information disclosure in Lenovo Help Android application

> Insufficient access control in the Lenovo Help Android app allows attackers to expose user email addresses and IMEI numbers.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-qh4g-vfjf-77wx

## What is CVE-2018-9067?

CVE-2018-9067 is a high-severity vulnerability in Lenovo Help Android application, published on 13 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Lenovo Help Android app versions earlier than 6.1.2.0327 had insufficient access control for some functions which, if exploited, could have led to exposure of approximately 400 email addresses and 8,500 IMEI.

## Which versions are affected by CVE-2018-9067?

It affects 1 product.


Products: Lenovo Lenovo Help.

## How do I fix CVE-2018-9067?

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

## Is CVE-2018-9067 being exploited?

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

## Other vulnerabilities in Lenovo Help Android application

- [CVE-2017-3776](https://insights.sbomify.com/CVE-2017-3776/): Information disclosure in Help mobile Android app (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-9067 and fix it if it is affected.

What it is: CVE-2018-9067 is a high-severity vulnerability in Lenovo Help Android application, published on 13 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-9067 in the wild and no public exploit code.

Affected product: Lenovo Help Android application. 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-2018-9067/ (Markdown: https://insights.sbomify.com/CVE-2018-9067/index.md)
```

## Sources

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

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