# CVE-2023-5080: Privilege escalation in Tablet

> Local applications can escalate privileges to access device identifiers and execute system commands on Lenovo tablets.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **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:** 19 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-qvvr-wcmf-4v5h

## What is CVE-2023-5080?

CVE-2023-5080 is a medium-severity vulnerability in Lenovo Tablet, published on 19 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A privilege escalation vulnerability was reported in some Lenovo tablet products that could allow local applications access to device identifiers and system commands.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2023-5080?

It affects 6 products.


Products: Lenovo Tab M10 Plus Gen 3 Tb125fu Firmware, Lenovo Tab M8 Hd Tb8505f Firmware, Lenovo Tab M8 Hd Tb8505fs Firmware, Lenovo Tab M8 Hd Tb8505x Firmware, Lenovo Tab M8 Hd Tb8505xs Firmware, Lenovo Tab P11 Pro Gen 2 Tb132fu Firmware.

## How do I fix CVE-2023-5080?

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

## Is CVE-2023-5080 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5080 and fix it if it is affected.

What it is: CVE-2023-5080 is a medium-severity vulnerability in Lenovo Tablet, published on 19 Jan 2024. 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-2023-5080 in the wild and no public exploit code.

Affected product: Lenovo Tablet. 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-2023-5080/ (Markdown: https://insights.sbomify.com/CVE-2023-5080/index.md)
```

## Sources

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

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