CVE-2022-20275
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 · uneditedIn DevicePolicyManager, there is a possible way to determine whether an app is installed, without query permissions, due to side channel information disclosure. 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-205836975
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 confidenceIn DevicePolicyManager, there is a possible way to determine whether an app is installed without query permissions due to side channel information disclosure. This allows a local attacker to enumerate installed applications without any special privileges, leading to local information disclosure.
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= 13.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Android versionGo to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADB shellAffected if Version is exactly 13.0 (not 12.x, 12L, or 14+)
-
Check Android security patch levelGo to Settings > About Phone > Security patch level or run 'getprop ro.build.version.security_patch' via ADB shellAffected if Security patch level is earlier than the Google fix date for CVE-2022-20275 (must be verified against Google's Android security bulletin for the month the fix was released)
-
Verify DevicePolicyManager componentThe vulnerability exists in the DevicePolicyManager system service; no user-facing feature needs to be enabled - any device running affected Android 13.0 with unpatched security level is potentially vulnerableAffected if Device runs Android 13.0 without the corresponding security patch applied
A device is affected if it runs Android version 13.0 and has not received the security update that addresses CVE-2022-20275 (check the Android security bulletin for the specific patch date).
Generated from the published advisory. Verify against your own configuration.
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 · scopedThis vulnerability requires a patch from Google in the Android framework. Users should ensure devices receive the latest Android security updates. There is no application-level remediation; the fix must come from the OS/vendor.
Android 13 with December 2022 security patch level or later
- 1. Navigate to Settings on the Android 13 device
- 2. Scroll down and select 'System'
- 3. Tap on 'Security & privacy' or 'Privacy'
- 4. Select 'Security update' or 'Google Play system update'
- 5. Check for and install any available security updates
- 6. Ensure the device is updated to at least the December 2022 security patch level or later
- 7. Verify the update was applied by checking the Android security patch level in Settings > System > About phone > Android version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20275 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-20275 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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