# CVE-2021-3720: Information disclosure in Legion Phone Pro (L79031)

> An information disclosure flaw in the Time Weather widget allows other applications to access device GPS data on Lenovo Legion Phones.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-86m9-qv63-94gq

## What is CVE-2021-3720?

CVE-2021-3720 is a medium-severity vulnerability in Lenovo Legion Phone Pro (L79031), published on 12 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An information disclosure vulnerability was reported in the Time Weather system widget on Legion Phone Pro (L79031) and Legion Phone2 Pro (L70081) that could allow other applications to access device GPS data.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2021-3720?

It affects 2 products.


Products: Lenovo Legion Phone2 Pro \(L70081\) Firmware, Lenovo Legion Phone Pro \(L79031\)firmware.

## How do I fix CVE-2021-3720?

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

## Is CVE-2021-3720 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3720 and fix it if it is affected.

What it is: CVE-2021-3720 is a medium-severity vulnerability in Lenovo Legion Phone Pro (L79031), published on 12 Nov 2021. 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-2021-3720 in the wild and no public exploit code.

Affected product: Lenovo Legion Phone Pro (L79031). 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-2021-3720/ (Markdown: https://insights.sbomify.com/CVE-2021-3720/index.md)
```

## Sources

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

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