dbcve.org
AndroidOperating system · Google

CVE-2022-23729

HIGH · 7.8 CVSS v3.1 Published 2022-03-04
Fix available
A fix is available. Upgrade to 11.0 or later.
See remediation →
80/100
Remediation priority · High
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
When the device is in factory state, it can be access the shell without adb authentication process. The LG ID is LVE-SMP-210010.

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

This vulnerability allows unauthenticated shell access via ADB on LG devices when in factory state. In the factory default configuration, ADB authentication requirements are not enforced, enabling an attacker with local access to obtain a shell with elevated privileges without proper credentials.

MitigationLG should issue a firmware patch that enforces ADB authentication even in factory state. Users should avoid leaving devices in factory state and should apply vendor-provided security updates promptly.

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:< 11.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Confirm device is an LG model
    Check the device manufacturer and model via 'Settings > About Phone > Manufacturer' or by running 'getprop ro.product.manufacturer' or 'getprop ro.product.brand' over ADB or in recovery mode
    Affected if Device is not an LG-branded device (the vulnerability specifically affects LG devices)
  2. Check Android OS version
    Navigate to 'Settings > About Phone > Android version' or run 'getprop ro.build.version.release' via ADB/shell
    Affected if Android version is below 11.0 (versions 10 and lower are within the affected range)
  3. Verify ADB is enabled on the device
    On the device, go to 'Settings > Developer Options > Android Debugging' (or 'Settings > System > Developer Options > USB Debugging' on newer versions), or check 'getprop persist.sys.usb.config' contains 'adb'
    Affected if ADB/debugging is currently enabled - the device is listening for ADB connections
  4. Assess whether device is in or near factory state
    Check if the device has been through initial setup wizard: look for presence of user-installed apps, user accounts configured, and custom configurations. Run 'pm list packages' to see installed packages - a factory-state device will have very few third-party packages
    Affected if Device is in fresh out-of-box factory state or has not had user configuration applied (this is the specific condition where ADB authentication is not enforced)

You are affected if you are using an LG device running Android version 10 or lower, with ADB debugging enabled, and the device is in or recently reset to factory default state with no user configuration applied.

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.

dbcve · scoped
Upgrade available Upgrade to 11.0 or later
Fixed in 11.0
Interim mitigation

LG should issue a firmware patch that enforces ADB authentication even in factory state. Users should avoid leaving devices in factory state and should apply vendor-provided security updates promptly.

Recommended fix Moderate confidence

Android 11.0 or later for LG devices

  1. 1. Back up all important data from the device
  2. 2. Ensure the device is charged to at least 50% battery
  3. 3. Navigate to Settings > System > Software Update on the LG device
  4. 4. Check for and install the Android 11.0 (or later) system update
  5. 5. After update completes, verify the fix by attempting ADB access from factory reset state - shell access should now require authentication
Caveat Standard Android upgrade considerations apply - review app compatibility and ensure data backup before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23729 — 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-2022-23729 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