dbcve.org
AndroidOperating system · Google

CVE-2022-20298

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 check if an account exists on the device 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-201416182

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's ContentService, a missing permission check allows local attackers to determine whether specific accounts exist on the device. This information disclosure vulnerability requires User execution privileges but needs no user interaction.

MitigationApply Android platform security updates (Android-13 patch level) to receive the ContentService permission fix. Until then, consider limiting device access to untrusted users.

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 equals 13.0 exactly (this CVE affects only Android 13.0)
  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 Patch level is earlier than the Android-13 security update that fixes this vulnerability (the specific date varies by carrier/device)
  3. Test ContentService account enumeration
    Use a test app or adb command to query ContentService for account information without holder accounts permission, e.g., attempt to query content://accounts or use AccountManager APIs without GET_ACCOUNTS permission
    Affected if Untrusted apps or shell users can successfully query whether specific account types exist on the device (successful enumeration indicates vulnerability is present)

A device is affected if it runs Android 13.0 and has not received the Android-13 security patch that fixes the ContentService permission check, allowing unauthorized enumeration of device accounts.

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 Android platform security updates (Android-13 patch level) to receive the ContentService permission fix. Until then, consider limiting device access to untrusted users.

Recommended fix Moderate confidence

Android 13.0 with latest security patch level (check Android Security Bulletin for specific month containing CVE-2022-20298 fix)

  1. Open Settings on the Android device
  2. Navigate to System > Security & privacy (or System > Update on some devices)
  3. Tap on "Update" or "Check for updates" to check for available updates
  4. Download and install the latest Android security patch update for Android 13
  5. After the update installs, verify the patch level by going to Settings > About Phone > Android version or Settings > System > Developer Options > System UI to confirm the security patch level includes the fix for CVE-2022-20298 (Android-13 security patch level containing fix)

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-20298 — 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-20298 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