CVE-2021-30162
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 4.4 through 11 software. Attackers can leverage ISMS services to bypass access control on specific content providers. The LG ID is LVE-SMP-210003 (April 2021).
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 LG mobile devices running Android 4.4 through 11 allows attackers to bypass access control on specific content providers by leveraging LG's ISMS (Integrated Security Management System) services. The flaw enables unauthorized access to sensitive data that should be protected by Android's content provider permission model.
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= 4.4= 4.4.1= 4.4.2= 4.4.3= 4.4.4= 5.0= 5.0.1= 5.0.2= 5.1= 5.1.0= 5.1.1= 6.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 device manufacturerCheck if the device is an LG mobile device by querying the system property 'ro.product.manufacturer' or checking the device model information in Settings > About PhoneAffected if The device is not manufactured by LG, as this vulnerability specifically affects LG mobile devices
-
Check the Android versionRetrieve the Android version via Settings > About Phone > Android version or by running 'getprop ro.build.version.release' in ADB shellAffected if The Android version falls between 4.4 and 11 inclusive, as this is the vulnerable range per the CVE description
-
Verify LG ISMS service presenceCheck for the presence of LG ISMS (Integrated Security Management System) by listing running services or checking for packages containing 'isms' in the package manager via ADB: 'dumpsys package | grep -i isms'Affected if The LG ISMS service is installed and running on the device, as the vulnerability leverages this specific service to bypass content provider permissions
-
Check LG security patch levelQuery the LG security patch date via 'getprop ro.build.version.security_patch' in ADB shell or check in Settings > About Phone > Software info > Security patch levelAffected if The security patch level is earlier than April 2021 (LVE-SMP-210003), as devices without this specific LG patch remain vulnerable
A user is affected if they have an LG device running Android 4.4 through 11 with LG ISMS service present and a security patch level before April 2021.
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.
From vendor dataApply the LG security patch released in April 2021 (LVE-SMP-210003) or later. Organizations should inventory affected LG devices in their fleet and ensure patch deployment.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30162 — 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-2021-30162 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