dbcve.org
AndroidOperating system · Google

CVE-2020-28345

HIGH · 7.5 CVSS v3.1 Published 2020-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered on LG mobile devices with Android OS 10 software. The Wi-Fi subsystem may crash because of the lack of a NULL parameter check. The LG ID is LVE-SMP-200025 (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 confidence

On LG mobile devices running Android OS 10, the Wi-Fi subsystem lacks a NULL parameter check, which can cause the Wi-Fi subsystem to crash. This is a denial-of-service vulnerability that could be triggered by malicious or malformed Wi-Fi operations leading to a device crash.

MitigationApply vendor-specific security patches from LG as they become available. Organizations should inventory affected LG Android 10 devices and establish patch management processes to receive timely updates.

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
AndroidOperating system
Affected:= 10.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device manufacturer
    Check the device model and manufacturer via Settings > About Phone > Model, or run 'getprop ro.product.manufacturer' or 'getprop ro.product.brand' in ADB shell
    Affected if Device is not an LG/LG Electronics product - this CVE only affects LG mobile devices
  2. Confirm Android version is 10.0
    Check Android version via Settings > About Phone > Android version, or run 'getprop ro.build.version.release' in ADB shell
    Affected if Android version is anything other than 10.0 - this CVE only affects Android 10.0
  3. Verify Wi-Fi subsystem is enabled
    Check if Wi-Fi is turned on via Settings > Network & Internet > Wi-Fi, or check Wi-Fi state via 'settings get global wifi_on' in ADB shell
    Affected if Wi-Fi is disabled - the vulnerability requires the Wi-Fi subsystem to be active to be triggered

You are affected if you have an LG mobile device running Android 10.0 with Wi-Fi functionality enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-specific security patches from LG as they become available. Organizations should inventory affected LG Android 10 devices and establish patch management processes to receive timely updates.

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-28345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-28345 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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