dbcve.org
AndroidOperating system · Google

CVE-2021-1012

MEDIUM · 5.5 CVSS v3.1 Published 2021-12-15
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 onResume of NotificationAccessDetails.java, there is a possible way to determine whether an app is installed, without query permissions, due to side channel information disclosure. 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-195412179

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 12's NotificationAccessDetails.java, the onResume method leaks side-channel information that allows a local attacker to determine whether a specific app is installed on the device without requiring query permissions. This is a local information disclosure vulnerability with no user interaction needed.

MitigationFix the onResume method in NotificationAccessDetails.java to prevent side-channel information disclosure about installed apps, likely by removing or properly protecting the information leak that reveals app installation status.

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:= 12.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. Verify Android version is 12.0
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The device is running Android 12.0 specifically (not 12L, 13, or other versions)
  2. Confirm Notification Access settings are accessible
    Navigate to Settings > Apps > Special app access > Notification access, or search for 'Notification access' in Settings
    Affected if The Notification Access settings page is reachable on the device
  3. Identify the security patch level
    Go to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB shell
    Affected if The security patch level is earlier than the fix for CVE-2021-1012 (Android 12.0 patches released prior to the fix)
  4. Check if vulnerable NotificationAccessDetails component exists
    Use ADB to check for the component: 'dumpsys package com.android.settings | grep -i notificationaccess'
    Affected if The NotificationAccessDetails activity exists and is accessible without additional permissions

A device is affected if it is running Android 12.0 with a security patch level prior to the CVE-2021-1012 fix and has the Notification Access settings accessible to local users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Fix the onResume method in NotificationAccessDetails.java to prevent side-channel information disclosure about installed apps, likely by removing or properly protecting the information leak that reveals app installation status.

Recommended fix Moderate confidence

Android 12.0 with January 2022 security patch level or later

  1. Ensure the device is running the latest Android security patch level for Android 12.0
  2. Go to Settings > Security > Security update and check for available updates
  3. Install any pending security updates that include the fix for CVE-2021-1012
  4. Verify the device is running a security patch level dated January 2022 or later (which contains the fix for this vulnerability)
Caveat Standard security update - minimal risk; updates only address the specific vulnerability without changing functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1012 — 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-2021-1012 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