CVE-2019-20783
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 7.0, 7.1, 7.2, 8.0, and 8.1 (North America CDMA) software. The LTE protocol implementation allows a bypass of AKA (Authentication and Key Agreement). The LG ID is LVE-SMP-180014 (February 2019).
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 allows bypass of AKA (Authentication and Key Agreement) in the LTE protocol implementation on affected LG mobile devices running Android 7.0-8.1. This critical flaw enables attackers to potentially impersonate devices or conduct man-in-the-middle attacks on LTE networks by circumventing the fundamental authentication mechanism that secures 4G/LTE connections.
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= 7.0= 7.1= 7.2= 8.0= 8.1CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 device manufacturerCheck if the device is an LG mobile device by going to Settings > About Phone > Manufacturer or running 'getprop ro.product.manufacturer' via ADBAffected if Device is not manufactured by LG - the vulnerability affects only LG mobile devices
-
Check Android OS versionGo to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADBAffected if Android version is 7.0, 7.1, 7.2, 8.0, or 8.1 - versions outside this range are not affected
-
Verify LTE baseband firmwareCheck the baseband/modem firmware version via 'getprop gsm.version.baseband' or 'getprop ro.baseband' via ADB - contact LG support to confirm if the specific baseband build includes the security fixAffected if Cannot verify patch status from OS level - the vulnerability exists in the LTE protocol implementation in the baseband firmware, and the patch status requires vendor confirmation
User is affected if they are using an LG mobile device with Android 7.0-8.1 and the LTE baseband firmware has not been updated with the security patch
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 vendor-supplied firmware/security updates from LG promptly. Until patches are available, users on affected devices should exercise caution when connecting to untrusted LTE networks and consider using VPN services as an additional security layer.
- Consultation8.0 h
- Implementation2.0 h
- Testing16.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,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20783 — 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-2019-20783 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