CVE-2021-0570
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 sendBugreportNotification of BugreportProgressService.java, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-178803845
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 sendBugreportNotification of BugreportProgressService.java on Android 11, an unsafe PendingIntent allows a local attacker to bypass permission checks and escalate privileges. The PendingIntent lacks proper protection (likely missing explicit package/component specification or proper mutability flags), enabling a malicious local app to hijack the intent and execute actions with the service's elevated permissions.
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= 11.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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 11.0Run 'getprop ro.build.version.sdk' or check Settings > About Phone > Android version. Android 11 corresponds to API level 30.Affected if The device runs Android 11.0 (API level 30)
-
Verify BugreportProgressService existsCheck for the presence of the BugreportProgressService component in the Android framework. On a rooted device, examine /system/framework/services.jar or decompile to locate 'com/android/server/BugreportProgressService'.Affected if The BugreportProgressService is present and enabled on the device
-
Inspect PendingIntent creation in sendBugreportNotificationDecompile or inspect the BugreportProgressService.java source code, specifically the sendBugreportNotification method. Locate the PendingIntent creation using 'PendingIntent.getService' or 'PendingIntent.getBroadcast'.Affected if The PendingIntent is created without an explicit component/package name (setComponent/setClassName) and without explicit mutability flags (FLAG_MUTABLE or FLAG_IMMUTABLE)
-
Check if bugreport notification feature is accessibleVerify the bugreport sharing functionality is accessible to other apps. Test if a local app can interact with the BugreportProgressService or receive the broadcast from sendBugreportNotification.Affected if The bugreport notification can be intercepted or manipulated by a local malicious app
A device is affected if it runs Android 11.0 and contains the vulnerable BugreportProgressService code with an unsafe PendingIntent lacking explicit component specification and proper mutability flags.
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.
From vendor dataEnsure PendingIntent is created with explicit component/package and appropriate mutability flags (FLAG_MUTABLE or FLAG_IMMUTABLE) to prevent intent hijacking. Apply Android framework security patches for Android-11.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0570 — 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-0570 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