dbcve.org
AndroidOperating system · Google

CVE-2022-20303

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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 ContentService, there is a possible way to determine if an account is on the device without GET_ACCOUNTS permission due to a missing permission check. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-200573021

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

In Android-13's ContentService, a missing permission check allows local apps to determine if accounts exist on the device without holding the GET_ACCOUNTS permission. This enables unauthorized enumeration of account presence, constituting a local information disclosure vulnerability.

MitigationApply the Google security patch for Android-13 that addresses the missing permission check in ContentService. Until the patch is available, monitor for apps requesting excessive account-related permissions.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 shell
    Affected if Version is exactly 13.0 (Android 13)
  2. Verify security patch level
    Go to Settings > About Phone > Security patch level or run 'getprop ro.build.version.security_patch' via adb shell
    Affected if The security patch level is earlier than the Google security update that addresses CVE-2022-20303 (patch date not specified in provided data)
  3. Audit account-related permissions
    Run 'dumpsys package <package_name>' for suspicious apps and check for GET_ACCOUNTS, AUTHENTICATE_ACCOUNTS, or USE_CREDENTIALS permissions in the manifest
    Affected if Apps without legitimate need hold GET_ACCOUNTS permission, which could be used in conjunction with this vulnerability
  4. Monitor ContentService access
    Use logcat to filter for ContentService account queries: 'adb logcat | grep -i account' and review for apps querying account presence without GET_ACCOUNTS
    Affected if Apps query account existence without holding the GET_ACCOUNTS permission

Device is affected if running Android 13.0 and the Google security patch for CVE-2022-20303 has not been applied, as the missing permission check in ContentService allows unauthorized account enumeration.

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 Google security patch for Android-13 that addresses the missing permission check in ContentService. Until the patch is available, monitor for apps requesting excessive account-related permissions.

Recommended fix High confidence

Android 13.0 to Android 13.x with September 2022 security patch level or later

  1. 1. Go to Settings on the Android device
  2. 2. Navigate to System > System update (or Settings > About Phone > System update)
  3. 3. Check for and install any available system updates
  4. 4. Ensure the device receives the Android Security Patch Level that includes the fix for A-200573021
Caveat Standard Android upgrade considerations apply - review app compatibility and backup data before updating

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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