AndroidOperating system · Google

CVE-2023-21397

HIGH · 7.8 CVSS v3.1 Published 2023-10-30
Fix available
A fix is available. Upgrade to 14.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
In Setup Wizard, there is a possible way to save a WiFi network due to an insecure default value. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

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 Android vulnerability in the Setup Wizard involves an insecure default value that allows saving a WiFi network, leading to local privilege escalation without requiring additional execution privileges or user interaction. The flaw enables a malicious or compromised application to potentially elevate its privileges through the Setup Wizard component's improper default configuration.

MitigationApply the latest Android security patch level (SPL) from the device OEM, which should include the fix for this insecure default value in Setup Wizard. Organizations should ensure mobile device management (MDM) policies restrict network configuration access until patches are applied.

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:< 14.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. Check Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if The installed Android version is 13.x or lower (below 14.0)
  2. Confirm Setup Wizard presence
    Check if the Setup Wizard app package exists: run 'pm list packages | grep setup' via ADB, or verify the device has gone through initial setup
    Affected if The device has the Setup Wizard component (standard on all Android devices)
  3. Verify security patch level
    Go to Settings > About Phone > Security Patch Level, or run 'getprop ro.build.version.security_patch' via ADB
    Affected if The security patch level is earlier than the fix date for CVE-2023-21397 (the vulnerability exists in unpatched versions)

A device is affected if it runs Android versions below 14.0 and has not received the corresponding security patch that addresses the insecure default value in Setup Wizard.

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 14.0 or later
Fixed in 14.0
Interim mitigation

Apply the latest Android security patch level (SPL) from the device OEM, which should include the fix for this insecure default value in Setup Wizard. Organizations should ensure mobile device management (MDM) policies restrict network configuration access until patches are applied.

Recommended fix High confidence

Android 14.0 (API level 34)

  1. Verify your device model is supported for Android 14.0 (API level 34) upgrade by checking the device manufacturer's update compatibility list
  2. Back up all important data from the device before performing the system update
  3. Navigate to Settings > System > Software Update (or Settings > About Phone > System Update on some devices)
  4. Check for available updates and download the Android 14.0 update if available
  5. Install the Android 14.0 system update following the on-screen prompts
  6. After update completion, verify the device is running Android 14.0 by checking Settings > About Phone > Android version
Caveat Full device wipe may be required during major Android version upgrades; some apps may not be compatible with Android 14

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-21397 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-21397 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