dbcve.org
AndroidOperating system · Google

CVE-2022-20322

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 PackageManager, there is a possible installed package disclosure due to a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-187176993

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

In Android's PackageManager, a missing permission check allows local apps or processes to enumerate installed packages without proper authorization. This enables an unprivileged local attacker to discover what applications are installed on the device, potentially revealing sensitive or private application information.

MitigationApply the Android-13 security update containing the fix for A-187176993. For organizations managing Android devices, ensure fleet devices receive the relevant patch. For AOSP-based product developers, integrate the upstream fix into their custom builds.

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
    Run 'getprop ro.build.version.release' in a shell or check Settings > About Phone > Android version
    Affected if Version is 13.0 (the specific affected version)
  2. Check security patch level
    Run 'getprop ro.build.version.security_patch' in a shell or check Settings > About Phone > Security patch level
    Affected if Patch level is earlier than the September 2022 Android 13 security update (or unknown/not set)
  3. Verify PackageManager behavior
    Use an app or script to query PackageManager for installed packages without holding any special permissions - observe if packages are returned without requiring QUERY_ALL_PACKAGES permission
    Affected if Installed packages are enumerateable without QUERY_ALL_PACKAGES permission on Android 13.0 devices

A device is affected if it runs Android 13.0 and has a security patch level prior to the fix for A-187176993 (the September 2022 Android security update or later required for remediation, but detection is satisfied by confirming Android 13.0 and pre-patch security level).

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 containing the fix for A-187176993. For organizations managing Android devices, ensure fleet devices receive the relevant patch. For AOSP-based product developers, integrate the upstream fix into their custom builds.

Recommended fix Moderate confidence

Android 13 with December 2022 security patch level or later; Android 14+ recommended

  1. 1. Check the current Android version and security patch level on the device in Settings > About Phone > Android version
  2. 2. Go to Settings > System > Security Update to verify the device has the latest security patches
  3. 3. If available, update to the latest Android 13 security patch level (recommended: December 2022 or later)
  4. 4. Alternatively, upgrade to a newer Android version (Android 14 or later) which includes the fix for this vulnerability
  5. 5. After updating, verify in Settings > About Phone that the security patch level reflects the update
Caveat Minimal risk - security update only; some device manufacturers may have varying update schedules

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

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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