dbcve.org
AndroidOperating system · Google

CVE-2022-20299

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 the given 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-201415895

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 missing permission check in Android's ContentService allows local applications to determine whether specific accounts exist on the device without proper authorization. This enables unauthenticated local information disclosure about user accounts present on the device.

MitigationApply the vendor-supplied Android security patch for Android-13 that addresses the missing permission check in ContentService. Organizations should ensure devices receive timely system updates.

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 is 13.0
    Run 'getprop ro.build.version.release' in ADB shell or check Settings > About Phone > Android version. This vulnerability affects only Android 13.0 specifically, not other versions.
    Affected if The version shown is exactly 13.0 (not 12.x, 14.x, or other 13.x variants)
  2. Verify ContentService is present
    Check if ContentService is running or accessible on the device by examining running services via 'dumpsys' or reviewing the system service registry.
    Affected if ContentService is present and exposed on the device
  3. Check security patch level
    Run 'getprop ro.build.version.security_patch' in ADB shell to see the installed security patch date.
    Affected if The security patch level predates the fix for CVE-2022-20299 (patch date is older than the vendor release addressing this issue)
  4. Test for unauthorized account enumeration
    Use a third-party app or ADB command to query account information through ContentService without holding the GET_ACCOUNTS permission. Observe if the query returns account presence information.
    Affected if Apps without GET_ACCOUNTS permission can successfully query and determine whether specific accounts exist on the device

The device is affected if it runs Android exactly version 13.0 and has not received the security patch that adds proper permission enforcement to ContentService for account queries.

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 vendor-supplied Android security patch for Android-13 that addresses the missing permission check in ContentService. Organizations should ensure devices receive timely system updates.

Recommended fix Moderate confidence

Android 14 or later, or Android 13 with December 2022 security patch level or higher

  1. 1. Check the current Android version on the device in Settings > About Phone > Android version
  2. 2. Navigate to Settings > System > Software Update (or Settings > About Phone > System Update)
  3. 3. Check for and install any available system updates
  4. 4. If updates are available, download and install them to receive the security patch containing the fix for CVE-2022-20299
  5. 5. Alternatively, consider upgrading to Android 14 or later if the device is eligible, as newer major versions include all previous security fixes
Caveat Major Android version upgrades may introduce UI changes or remove legacy features; verify app compatibility before upgrading

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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