CVE-2020-13839
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.2, 8.0, 8.1, 9, and 10 (MTK chipsets). Code execution can occur via a custom AT command handler buffer overflow. The LG ID is LVE-SMP-200007 (June 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 · high confidenceA buffer overflow vulnerability in the custom AT command handler on LG mobile devices with MediaTek chipsets allows remote code execution. The flaw exists across Android OS versions 7.2 through 10 and can be exploited by sending specially crafted AT commands to the modem.
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.2= 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
- 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.
-
Identify device manufacturerCheck the device settings or use 'getprop ro.product.manufacturer' or 'getprop ro.product.brand' in ADB shell to confirm the device is LGAffected if The device manufacturer is not LG - if not LG, the device is not affected by this specific LG vulnerability
-
Identify chipset vendorCheck device specs or use 'getprop ro.mediatek.platform' in ADB shell to confirm MediaTek chipsetAffected if The device does not use a MediaTek chipset - the vulnerability is specific to MediaTek-based LG devices
-
Check Android OS versionUse 'getprop ro.build.version.release' in ADB shell or check Settings > About Phone > Android versionAffected if The Android version is outside 7.2 through 10 - versions outside this range are not affected according to the specified affected versions
-
Verify AT command interface accessibilityCheck if the modem AT interface is exposed. Common paths include /dev/smd0, /dev/ttyUSB0, or /dev/ttyACM0. Use 'ls -la /dev/smd*' or 'ls -la /dev/tty*' in ADB shell to list available modem interfacesAffected if The AT command interface is accessible from apps or ADB without proper restrictions - an exposed AT interface is required for exploitation
The device is affected if it is an LG mobile phone with a MediaTek chipset running Android 7.2 through 10, and the modem AT command interface is accessible for injection.
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 (LG ID LVE-SMP-200007). Until patches are available, consider network-level controls to restrict untrusted AT command injection and restrict device access to trusted networks.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.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 $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13839 — 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-13839 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