CVE-2018-14982
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 · uneditedCertain LG devices based on Android 6.0 through 8.1 have incorrect access control in the GNSS application. The LG ID is LVE-SMP-180004.
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 confidenceIncorrect access control in the GNSS (Global Navigation Satellite System) application on LG Android devices running versions 6.0 through 8.1 allows unauthorized access to location/GPS functionality. The CVSS 9.8 score indicates this is exploitable over the network with no authentication required and likely leads to complete compromise of location data or related system 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= 6.0= 6.0.1= 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
- High
CVSS:3.0/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 if the device is manufactured by LG. This can be done via device settings under 'About phone' > 'Brand' or 'Manufacturer', or by checking the device model number against LG product listings.Affected if The device is an LG-branded Android device
-
Check Android OS versionNavigate to Settings > About phone > Android version. Confirm the exact version number matches 6.0, 6.0.1, 7.0, 7.1, 7.2, 8.0, or 8.1.Affected if The Android version is 6.0, 6.0.1, 7.0, 7.1, 7.2, 8.0, or 8.1
-
Locate GNSS applicationCheck for the presence of GNSS-related applications in the device application list. The vulnerable component is the GNSS (Global Navigation Satellite System) location service application. Access via Settings > Apps > All apps and search for 'GNSS', 'Location', or 'GPS' related system applications.Affected if The GNSS application is installed and present on the device
-
Verify location permissions configurationExamine the GNSS/location application permissions by going to Settings > Apps > [GNSS/Location App] > Permissions. The vulnerability allows unauthorized access, meaning the app may have overly permissive access settings.Affected if The GNSS application has location permissions enabled without proper access controls
If the device is an LG Android device running versions 6.0 through 8.1 with the GNSS application present, the environment is likely affected by this vulnerability.
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-provided security updates from LG; if unavailable, consider network segmentation to limit exposure of affected devices and restrict application permissions where possible.
- Consultation4.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 $2,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14982 — 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-2018-14982 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