dbcve.org
AndroidOperating system · Google

CVE-2022-20248

HIGH · 7.8 CVSS v3.1 Published 2022-08-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Settings, there is a possible way to connect to an open network bypassing DISALLOW_CONFIG_WIFI restriction due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-227619193

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 confidence

A logic error in the Android Settings app allows bypassing the DISALLOW_CONFIG_WIFI restriction, enabling connection to open networks when this should be prohibited. This enables local privilege escalation without user interaction or additional execution privileges, affecting Android-13 devices.

MitigationApply the Android security patch level for the month this vulnerability was fixed (typically December 2022 or later). Organizations using device policy controllers should verify the restriction is properly enforced after updating.

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:= 13.0.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
    Navigate to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADB shell
    Affected if Version is exactly 13.0.0 (the only affected version listed)
  2. Check if device is managed by MDM/ DPC
    Navigate to Settings > Security & privacy > Device admin or check for installed device policy controller apps; run 'dpm list-active-admins' via ADB shell
    Affected if Device has a device policy controller configured that enforces DISALLOW_CONFIG_WIFI restriction
  3. Verify WiFi configuration restriction is enforced
    Attempt to access WiFi settings > check if 'Add Wi-Fi network' or 'Save networks' options are disabled/grayed out, or check via DPC API if restriction is active
    Affected if The DISALLOW_CONFIG_WIFI restriction is configured but user can still connect to open networks through Settings app (bypass exists)
  4. Inspect Settings app package
    Run 'pm list packages -3' and check 'com.android.settings' package version via 'dumpsys package com.android.settings' in ADB shell
    Affected if Package version corresponds to Android 13.0.0 build and contains the vulnerable Settings app

Device is affected if it runs Android 13.0.0 exactly and has DISALLOW_CONFIG_WIFI restriction policy applied, allowing unauthorized open WiFi connections that should be blocked.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch level for the month this vulnerability was fixed (typically December 2022 or later). Organizations using device policy controllers should verify the restriction is properly enforced after updating.

Recommended fix High confidence

Android 13 with December 2022 security patch level (or later)

  1. Navigate to Settings > System > Security Update on the Android device
  2. Check the Android security patch level
  3. If the patch level is earlier than December 2022, initiate a system update to receive the latest security patches
  4. Verify the update was applied by checking Settings > System > Security Update shows December 2022 or later patch level
Caveat Standard Android update risks apply - some apps may have compatibility issues with newer Android versions

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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