CVE-2020-25058
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, and 10 software. The network_management service does not properly restrict configuration changes. The LG ID is LVE-SMP-200012 (July 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 confidenceThe network_management service on LG mobile devices running Android 8.0, 8.1, 9, and 10 lacks proper access control restrictions, allowing unrestricted modification of network configuration settings. This critical flaw (CVSS 9.8) could enable an unauthenticated attacker to manipulate network parameters, potentially facilitating man-in-the-middle attacks, traffic interception, or service disruption.
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
- 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 system properties to confirm the device is made by LG. On Android, go to Settings > About Phone > Manufacturer or run 'getprop ro.product.manufacturer' via ADB.Affected if Device manufacturer is not LG - the vulnerability only affects LG mobile devices
-
Confirm Android versionCheck the Android version in Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB.Affected if Android version is 8.0, 8.1, 9.0, or 10.0 - these are the affected versions per the CVE
-
Verify network_management service presenceCheck if the network_management service is exposed on the device. Run 'dumpsys | grep network_management' or examine the service list via ADB with 'dumpsys -l | grep network' to see if the service exists.Affected if The network_management service is present and running on the device
-
Test service accessibilityAttempt to interact with the network_management service through Android debugging or examine service permissions. Use 'appops' or check the service's manifest definition for the network_management operation.Affected if The service allows unrestricted access without proper authentication or permission checks - this indicates the vulnerability is present
A user is affected if they own an LG mobile device running Android 8.0, 8.1, 9.0, or 10.0 with the vulnerable network_management service exposed and lacking access controls.
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 LG's July 2020 security update (LVE-SMP-200012) to all affected devices. Until patched, restrict device usage to trusted networks and disable unused network interfaces to reduce attack surface.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25058 — 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-25058 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