AndroidOperating system · Google

CVE-2022-20254

HIGH · 8.8 CVSS v3.1 Published 2022-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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 Wi-Fi, there is a permissions bypass. This could lead to local escalation of privilege from the guest user with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-223377547

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

A permissions bypass vulnerability in the Wi-Fi component of Android 13 allows a local guest user to escalate privileges without any additional execution privileges or user interaction. This is a local privilege escalation (LPE) flaw in the Wi-Fi subsystem that enables a guest account to bypass intended permission boundaries.

MitigationApply the Android 13 security update that includes the fix for this vulnerability. Organizations should ensure their Android device fleet is receiving and deploying monthly security patches, particularly the patch level that addresses A-223377547.

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

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

CVSS:3.1/AV:A/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 checks

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

  1. Verify Android version
    Check the device Settings > About Phone > Android version to confirm it is exactly 13.0
    Affected if The device is running Android 13.0 (not 13.1, 13.2, or later)
  2. Check security patch level
    Navigate to Settings > About Phone > Security patch level and note the date. Compare against the patch date for A-223377547.
    Affected if The security patch level is older than the fix date for CVE-2022-20254, meaning the vulnerability has not been addressed
  3. Confirm Wi-Fi component is present
    Verify the device has Wi-Fi capability enabled by checking Settings > Network & Internet > Wi-Fi is toggled on
    Affected if Wi-Fi is enabled and the device runs Android 13.0 with an unpatched security level
  4. Identify user account type exposure
    Check if the device has guest or secondary user accounts configured under Settings > System > Multiple users (or Settings > Accounts > Other users)
    Affected if A guest or secondary user account exists on an unpatched Android 13.0 device, as the vulnerability enables such accounts to bypass permission boundaries

A user is affected if the device runs Android 13.0 specifically and has not received the security update addressing the Wi-Fi permissions bypass (A-223377547).

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 13 security update that includes the fix for this vulnerability. Organizations should ensure their Android device fleet is receiving and deploying monthly security patches, particularly the patch level that addresses A-223377547.

Recommended fix Moderate confidence

Android 13 with December 2022 Security Patch Level or later

  1. 1. Navigate to Settings on the Android device
  2. 2. Go to System > Software Update (or Security)
  3. 3. Check for and install any available system updates
  4. 4. Ensure the device receives the December 2022 Android Security Patch Level or later
  5. 5. After updating, verify the Wi-Fi permissions behave correctly for guest accounts

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,790
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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