CVE-2020-25282
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 · uneditedAn issue was discovered on LG mobile devices with Android OS 10 software. The lguicc software (for the LG Universal Integrated Circuit Card) allows attackers to bypass intended access restrictions on property values. The LG ID is LVE-SMP-200020 (September 2020).
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 vulnerability in the LG Universal Integrated Circuit Card (lguicc) software on Android OS 10 devices allows attackers to bypass intended access restrictions on property values. The issue enables unauthorized access to protected configuration or system properties related to the UICC/SIM card functionality, which could be chained with other attacks for further device compromise.
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= 10.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify Android version is exactly 10.0Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Android version shows 10.0 exactly - other versions are not affected
-
Confirm LG lguicc component is installedCheck for the lguicc package via 'pm list packages | grep lguicc' or inspect /system/app/lguicc/ via ADB shell if presentAffected if The lguicc package exists on the device - the flaw is in this LG-specific component
-
Check UICC property access permissionsInspect the lguicc configuration files in /data/data/com.lge.lguicc/ or /system/etc/lguicc/ for overly permissive access controls on UICC/SIM propertiesAffected if Protected UICC/SIM system properties are readable without proper authorization - the vulnerability allows this bypass
A device is affected if it runs Android 10.0 on an LG device with the lguicc component present and has the vulnerable permission configuration that allows unauthorized UICC property access.
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 · scopedApply the vendor-provided security patch (LG LVE-SMP-200020, September 2020) via official LG firmware updates for affected devices. Organizations should inventory impacted LG devices and deploy updates through their mobile device management infrastructure.
Android 11+ (if device is supported by LG)
- Check for available system/security updates on the LG device via Settings > System > Software Update or Settings > General > About phone > Software Update
- If no update is available, contact LG customer support or your mobile carrier for patch availability information
- Consider upgrading to Android 11 or later if the device hardware supports it, as the vulnerability is specific to Android 10.0
- Verify the LG security bulletin LVE-SMP-200020 for any carrier-specific patch deployment timelines
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25282 — 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-2020-25282 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