CVE-2020-0308
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 Window Manager, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-153654357
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 · moderate confidenceIn Android's Window Manager, an unsafe PendingIntent allows a permission bypass that could enable local information disclosure. The vulnerability requires user execution privileges but needs no user interaction. An attacker with code execution in a privileged context could potentially intercept or manipulate the PendingIntent to access sensitive window manager data.
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
- 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 11.0Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version. The vulnerability affects ONLY Android 11.0.Affected if The device is running Android 11.0 exactly. Earlier versions (10, 9, etc.) and later versions (12, 13) are not affected by this specific CVE.
-
Identify applications using Window Manager PendingIntentsReview application code or installed apps that interact with android.view.WindowManager. Check for any code that creates PendingIntent objects for Window Manager operations such as window callbacks, token management, or layout instructions.Affected if Applications create PendingIntent objects for Window Manager operations without FLAG_IMMUTABLE set.
-
Inspect PendingIntent flag configurationFor each PendingIntent found in Window Manager usage, examine whether FLAG_IMMUTABLE (0x00000040) or FLAG_MUTABLE (0x00000020) is explicitly set. Check source code or decompile APKs to inspect Intent.setFlags() or PendingIntent.getActivity/getService/getBroadcast calls.Affected if PendingIntents used with Window Manager do NOT have FLAG_IMMUTABLE set, making them mutable and vulnerable to interception.
-
Check for privileged context apps with permission to intercept IntentsReview installed applications holding elevated permissions (system apps, apps with signature|privileged permissions) that could potentially receive or intercept the exposed PendingIntents. Use 'dumpsys package <pkg>' to check permission grants.Affected if A malicious or compromised app with code execution in a privileged context can intercept the unsafe PendingIntent and access sensitive Window Manager data.
You are affected if your Android device runs version 11.0 and any application uses Window Manager with PendingIntents that lack the FLAG_IMMUTABLE flag, allowing a privileged attacker to intercept and access sensitive window data.
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 dataThe fix involves creating PendingIntents with appropriate immutability flags (FLAG_IMMUTABLE) and ensuring they are protected with proper permissions to prevent unauthorized access or interception by malicious applications.
- Consultation4.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0308 — 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-2020-0308 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