CVE-2021-1010
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 getSigningKeySet of PackageManagerService.java, there is 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-12Android ID: A-189857801
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 the getSigningKeySet function of PackageManagerService.java in Android 12, a permission check is missing. This allows a local attacker to potentially retrieve signing key set information without any elevated privileges or user interaction, 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= 12.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.
-
Confirm Android version is 12.0Go to Settings > About Phone > Android version and verify the version number is exactly 12.0Affected if Android version shows 12.0 (the only affected version per the CVE)
-
Check Security Patch LevelGo to Settings > About Phone > Security patch level and note the date. Compare against March 2022.Affected if Security patch level is earlier than March 2022 (vulnerable) or unavailable (assumed vulnerable)
-
Verify PackageManagerService accessibilityThis vulnerability is in the getSigningKeySet function of PackageManagerService. On affected devices, any local app could potentially call PackageManager.getPackageInfo with GET_SIGNING_KEYSETS flag without permission check to retrieve signing key information.Affected if Running Android 12.0 with security patch level before March 2022 allows the unprivileged access to signing key set data
Device is affected if it runs Android 12.0 and has a Security Patch Level earlier than March 2022, as the missing permission check in PackageManagerService.getSigningKeySet allows local information disclosure.
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 · scopedApply the Android security patch level for March 2022 or later to address the missing permission check in PackageManagerService. For enterprise deployments, ensure devices receive timely system updates and consider using MDM policies to enforce patch compliance.
Android 12L (Android 12.1) or January 2022 security patch for Android 12.0
- Upgrade to Android 12L (Android 12.1) or later, which contains the fix for CVE-2021-1010
- Alternatively, apply the January 2022 Android security patch update (patch level 2022-01-01) to Android 12.0
- Verify the fix by checking Settings > About Phone > Android version shows the updated patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1010 — 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-2021-1010 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