CVE-2020-28344
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 8.0, 8.1, 9.0, and 10 software. System services may crash because of the lack of a NULL parameter check. The LG ID is LVE-SMP-200024 (November 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 confidenceMissing NULL parameter check in system services on LG mobile devices running Android 8.0, 8.1, 9.0, and 10 causes system services to crash, resulting in denial of service. The vulnerability stems from the lack of input validation before passing parameters to system service functions.
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= 8.0= 8.1= 9.0= 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device manufacturerCheck device settings or run 'getprop ro.product.brand' or 'getprop ro.manufacturer' in ADB shell to confirm the device is LGAffected if The device is not an LG mobile device (this vulnerability only affects LG devices)
-
Check the Android versionRun 'getprop ro.build.version.release' in ADB shell or check Settings > About Phone > Android versionAffected if The Android version is 8.0, 8.1, 9.0, or 10.0
-
Verify the LG model is a mobile deviceRun 'getprop ro.product.model' in ADB shell to confirm it is a phone or tablet, not a different device typeAffected if The device is an LG mobile phone or tablet running the affected Android versions
-
Look for system service crash symptomsCheck device logs (logcat) or system crash reports in /data/data/com.android.providers.telephony/databases/ or check for repeated system service restart notificationsAffected if System services are crashing repeatedly without clear other cause on an affected LG device
-
Check for the specific vulnerability triggerMonitor for crashes triggered by specific system service calls that pass NULL parameters - this would typically manifest as sudden service disruptions when using certain featuresAffected if Service crashes occur during normal system service operations on an affected LG Android device
A user is affected if they are using an LG mobile device running Android 8.0, 8.1, 9.0, or 10.0 and are experiencing unexplained system service crashes or denial of service conditions.
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 vendor-supplied patch from LG (LVE-SMP-200024, November 2020). Until the patch is applied, monitor affected devices for service disruptions and consider restricting their use in critical business functions.
- Consultation2.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28344 — 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-28344 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