dbcve.org
AndroidOperating system · Google

CVE-2022-20219

MEDIUM · 5.5 CVSS v3.1 Published 2022-07-13
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 multiple functions of StorageManagerService.java and UserManagerService.java, there is a possible way to leave user's directories unencrypted due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12LAndroid ID: A-224585613

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 logic error in StorageManagerService.java and UserManagerService.java causes user directories to remain unencrypted when they should be encrypted. This is a local information disclosure vulnerability in Android's encryption handling that requires no user interaction or elevated privileges to exploit.

MitigationApply the Android security patch for the month containing this fix (refer to the Android Security Bulletin). Ensure devices receive timely system updates from device manufacturers.

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:= 10.0= 11.0= 12.0= 12.1

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' or 'getprop ro.android.build.version.sdk' in a shell, or go to Settings > About Phone > Android version
    Affected if The version shows 10.0, 11.0, 12.0, or 12.1 (or SDK 29, 30, 31, 32) - the device falls within the affected version range
  2. Verify file-based encryption is enabled
    Run 'getprop ro.crypto.type' to check if file-based encryption is in use, or check if /data is mounted with encryption by inspecting 'vdc volume list' output for encrypted data volumes
    Affected if File-based encryption is enabled but the logic error may still leave user directories unencrypted
  3. Check user directory encryption status
    Examine /data/user/ or /data/media/0 directories using 'ls -la' and verify if files show encryption indicators (fscrypt encryption flags) - compare actual encryption status against what should be enforced for the user profile
    Affected if User directories exist in /data but are NOT actually encrypted (no encryption attributes visible) despite being in a profile that should require encryption

The device is affected if it runs Android 10, 11, 12.0, or 12.1 AND file-based encryption shows user directories as unencrypted when they should be encrypted per the encryption policy.

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 the month containing this fix (refer to the Android Security Bulletin). Ensure devices receive timely system updates from device manufacturers.

Recommended fix Moderate confidence

Later Android security patch level (check source.android.com security bulletin for the specific release containing fix for A-224585613)

  1. Apply the latest Android security update for your device. Go to Settings > Security > Security update and ensure you have the latest patch level installed.
  2. If your device manufacturer provides updates, ensure you install the most recent system update that includes the fix for Android ID A-224585613.
  3. Verify the patch level by checking Settings > About Phone > Android version - the security patch level should be later than the version that contained the vulnerability.
Caveat Security updates typically have minimal breaking changes, but verify with your device manufacturer for any known issues

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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