dbcve.org
AndroidOperating system · Google

CVE-2022-20323

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 package installation disclosure 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-187176203

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 a local attacker to discover what packages are being installed on the device. This information disclosure vulnerability enables an app with basic user-level execution privileges to enumerate package installations without proper authorization, potentially revealing sensitive application usage information.

MitigationApply the Android security patch for CVE-2022-20323, which adds the missing permission check in PackageManager to restrict package installation disclosure to authorized system processes only.

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. Verify Android version
    Check the device's Android version in Settings > About Phone > Android version, or run `getprop ro.build.version.release` via ADB
    Affected if Version is exactly 13.0
  2. Check security patch level
    Check the security patch date in Settings > About Phone > Security patch level, or run `getprop ro.build.version.security_patch` via ADB
    Affected if Patch level is earlier than September 2022 or does not include the CVE-2022-20323 fix
  3. Confirm vulnerability context
    This CVE affects PackageManager's missing permission check that allows any app to enumerate package installations. The fix adds authorization checks to restrict this information to authorized system processes only.
    Affected if Device runs Android 13.0 without the September 2022 or later security update containing the CVE-2022-20323 patch

A user is affected if their device runs Android 13.0 with a security patch level earlier than the one that addresses the missing permission check in PackageManager.

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 security patch for CVE-2022-20323, which adds the missing permission check in PackageManager to restrict package installation disclosure to authorized system processes only.

Recommended fix Moderate confidence

Android 13 with October 2022 security patch level or later (or migrate to newer Android version with subsequent security updates)

  1. Check your device's current Android security patch level in Settings > About Phone > Android version
  2. Verify if your device has received the October 2022 Android Security Bulletin update or later
  3. If the security patch level is below October 2022, check for system updates in Settings > System > Software Update
  4. Install any available system updates that include the latest security patches
  5. After updating, verify the security patch level reflects the patched version in Settings > About Phone > Android version
Caveat Security patches are backward-compatible and should not introduce breaking changes; ensure device compatibility before upgrading major Android versions

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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