CVE-2023-5080
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA privilege escalation vulnerability was reported in some Lenovo tablet products that could allow local applications access to device identifiers and system commands.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a local privilege escalation vulnerability affecting Lenovo tablets that allows unprivileged local applications to access device identifiers (like serial numbers, IMEIs, etc.) and execute system commands they shouldn't have access to. The vulnerability likely stems from improper permission checks or exposed Android intents/services that should be restricted to system-level applications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 8505f_usr_s301106_2309140042_v9.56_bmp_row< 8505fs_usr_s301107_2309140028_v9.56_bmp_row< 8505x_usr_s301129_2309141226_v9.56_bmp_row< 8505xs_usr_s301077_2309140036_v9.56_bmp_row< tb125fu_usr_s100116_2311171525_mp1rc_row< tb132fu_s240219_231123_rowCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the tablet modelCheck the device model number in Settings > About Tablet or via 'getprop ro.product.model' commandAffected if Model number is Tb8505f, Tb8505fs, Tb8505x, Tb8505xs, Tb125fu, or Tb132fu
-
Check the firmware build versionNavigate to Settings > About Tablet > Build Number, or use 'getprop ro.build.version.incremental' via ADB shellAffected if Build version is below the specified threshold for your model
-
Compare against affected version rangesMatch your exact firmware version string to the affected ranges: Tab M8 HD models need versions below 8505f_usr_s301106_2309140042_v9.56_bmp_row (or equivalent for your variant), Tab M10 Plus Gen 3 needs below tb125fu_usr_s100116_2311171525_mp1rc_row, Tab P11 Pro Gen 2 needs below tb132fu_s240219_231123_rowAffected if Your installed firmware version is lower than the patched version for your specific model and variant
You are affected if you own one of the listed Lenovo tablet models and your current firmware version is older than the patched version threshold for that model.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8505xs_usr_s301077_2309140036_v9.56_bmp_row8505f_usr_s301106_2309140042_v9.56_bmp_row8505fs_usr_s301107_2309140028_v9.56_bmp_row
Apply the vendor-supplied system/firmware update from Lenovo. Organizations should inventory affected Lenovo tablet models, verify the patch status, and ensure devices are updated to the patched version.
8505f_usr_s301106_2309140042_v9.56_bmp_row and later for Tab M8 HD; tb125fu_usr_s100116_2311171525_mp1rc_row and later for Tab M10 Plus Gen 3; tb132fu_s240219_231123_row and later for Tab P11 Pro Gen 2
- 1. Identify the exact model number of the Lenovo tablet (TB8505f, TB8505fs, TB8505x, TB8505xs, TB125fu, or TB132fu)
- 2. Navigate to Lenovo's support website at support.lenovo.com
- 3. Enter the specific model number (e.g., TB8505f) in the product search or drivers download section
- 4. Locate the firmware/driver downloads for the tablet
- 5. Download and install the firmware version equal to or newer than: 8505f_usr_s301106_2309140042_v9.56_bmp_row (for TB8505f), 8505fs_usr_s301107_2309140028_v9.56_bmp_row (for TB8505fs), 8505x_usr_s301129_2309141226_v9.56_bmp_row (for TB8505x), 8505xs_usr_s301077_2309140036_v9.56_bmp_row (for TB8505xs), tb125fu_usr_s100116_2311171525_mp1rc_row (for TB125fu), or tb132fu_s240219_231123_row (for TB13
- 6. Follow the on-screen instructions to complete the firmware update
- 7. After update, verify the firmware version matches or exceeds the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5080 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-5080 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data