CVE-2020-0248
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 postInstantAppNotif of InstantAppNotifier.java, there is a possible permission bypass due to a PendingIntent error. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-154627439
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 postInstantAppNotif of InstantAppNotifier.java in Android 10, a PendingIntent configuration error allows a permission bypass enabling local information disclosure. An attacker with local device access can exploit this without user interaction.
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= 10.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.
-
Verify Android version is 10.0Check the installed Android version. On the device: go to Settings > About Phone > Android version. Via ADB: run 'getprop ro.build.version.release' and 'getprop ro.build.version.sdk'Affected if Android version is exactly 10.0 (API level 29). Versions 9, 11, and later are not affected by this specific CVE.
-
Check security patch levelCheck the installed Android security patch level. On the device: go to Settings > About Phone > Security patch level. Via ADB: run 'getprop ro.build.version.security_patch'Affected if Security patch level is earlier than 2020-10-01 (October 2020 patch). The vulnerability was fixed in the October 2020 Android security update.
-
Verify InstantAppNotifier component existsCheck for the vulnerable component. Via ADB shell, run 'dumpsys package com.android.systemui | grep -i instantappnotifier' or check the APK at /system/framework/framework-res.apkAffected if This confirms the component is present on the device (standard in Android 10), but version/patch level checks above are the definitive affected status.
Device is affected only if running Android 10.0 exactly with a security patch level earlier than October 2020; devices on other Android versions or with the October 2020 or later patch are not vulnerable.
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 dataThis is an Android framework vulnerability requiring a system-level update. Apply the October 2020 Android security patch or later to affected Android-10 devices. There is no application-level workaround.
- Consultation4.0 h
- Testing2.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 $2,336.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0248 — 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-0248 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