CVE-2021-1011
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 setPackageStoppedState 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-188219307
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 confidenceCVE-2021-1011 is a missing permission check vulnerability in the setPackageStoppedState function of PackageManagerService.java on Android-12. The absence of proper permission validation allows a local attacker to access package stopped state information without any elevated privileges or user interaction, resulting in 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.
-
Check Android versionRun 'settings get global os_version' or 'getprop ro.build.version.release' to retrieve the installed Android versionAffected if The version returned is exactly 12.0 (the equals sign indicates only version 12.0 is affected)
-
Verify build ID (optional)Run 'getprop ro.build.id' to get the specific build identifier for Android 12Affected if Build ID corresponds to Android 12 (such as SP1A.xxx or Sxxx) and version is 12.0
The device is affected only if it is running Android version 12.0 exactly; versions before or after 12.0 are not in the affected range.
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 appropriate permission check in the setPackageStoppedState method of PackageManagerService.java to ensure only authorized callers can modify or query package stopped state information.
Apply Android security update containing the fix (Android Security Patch Level addressing CVE-2021-1011)
- 1. Check the Android Security Patch Level on the device: Go to Settings > About Phone > Security Patch Level
- 2. Verify the device has received the Android Security Bulletin patch for the month addressing CVE-2021-1011
- 3. If the device is on Android 12.0 (S) and does not have the latest security update, check for system updates in Settings > System > Software Update
- 4. Apply all available system updates to ensure the security patch containing the fix for CVE-2021-1011 is installed
- 5. For device manufacturers: Ensure the device receives the Android security update that includes the fix for A-188219307 in the PackageManagerService framework component
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1011 — 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-1011 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