dbcve.org
AndroidOperating system · Google

CVE-2020-0400

MEDIUM · 5.5 CVSS v3.1 Published 2020-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
In showDataRoamingNotification of NotificationMgr.java, 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-11 Android-10Android ID: A-153356561

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 confidence

In Android's NotificationMgr.java, the showDataRoamingNotification method creates an unsafe PendingIntent that can be exploited by malicious applications to intercept or manipulate the notification intent. This allows unauthorized apps to access sensitive data roaming information without proper permissions, resulting in local information disclosure.

MitigationUpdate the PendingIntent creation in NotificationMgr.java to use secure flags such as FLAG_IMMUTABLE or FLAG_MUTABLE with proper permission validation, ensuring the intent cannot be intercepted or hijacked by other applications.

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
AndroidOperating system
Affected:= 10.0= 11.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Android version
    On the device, go to Settings > About Phone > Android version. Alternatively, run 'adb shell getprop ro.build.version.release'
    Affected if The version is 10.0 or 11.0 exactly (as specified in the affected versions)
  2. Locate NotificationMgr.java in the Android framework
    Search the Android platform source code for the file NotificationMgr.java, typically found in frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/ or similar SystemUI paths
    Affected if The file exists in the codebase and contains the showDataRoamingNotification method
  3. Inspect showDataRoamingNotification method for PendingIntent creation
    Open NotificationMgr.java and locate the showDataRoamingNotification method. Search for 'PendingIntent.getBroadcast' or 'PendingIntent.getActivity' calls within this method
    Affected if A PendingIntent is created without FLAG_IMMUTABLE or FLAG_MUTABLE flags (these flags were introduced in API 31, so the vulnerability exists in versions without them)
  4. Verify the PendingIntent flags used
    In the PendingIntent creation call, check if 'PendingIntent.FLAG_IMMUTABLE' or 'PendingIntent.FLAG_MUTABLE' is explicitly included in the flags parameter
    Affected if Neither FLAG_IMMUTABLE nor FLAG_MUTABLE is present in the PendingIntent creation, leaving it exploitable
  5. Check for data roaming notification usage
    Verify that the showDataRoamingNotification method handles data roaming alerts and that its PendingIntent contains sensitive data roaming information in the intent extras
    Affected if The method processes data roaming notifications and the intent carries roaming-related data that could be intercepted

A device or system is affected if it runs Android 10.0 or 11.0 and the NotificationMgr.java source code contains a PendingIntent in showDataRoamingNotification that lacks FLAG_IMMUTABLE or FLAG_MUTABLE flags.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the PendingIntent creation in NotificationMgr.java to use secure flags such as FLAG_IMMUTABLE or FLAG_MUTABLE with proper permission validation, ensuring the intent cannot be intercepted or hijacked by other applications.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-0400 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-0400 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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