dbcve.org
AndroidOperating system · Google

CVE-2021-1019

HIGH · 7.3 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 →
73/100
Remediation priority · Elevated

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 snoozeNotification of NotificationListenerService.java, there is a possible permission confusion due to a misleading user consent dialog. This could lead to local escalation of privilege with User execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-12Android ID: A-195031401

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 confidence

In Android 12's NotificationListenerService snoozeNotification function, a permission confusion vulnerability exists where a misleading user consent dialog can trick users into granting elevated privileges, leading to local privilege escalation.

MitigationApply the Android security patch for CVE-2021-1019 when released via system updates; users should exercise caution with unexpected permission dialogs.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 checks

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

  1. Confirm Android version
    Check system settings > About Phone > Android version. The device must be running Android 12.0 exactly for this vulnerability to apply.
    Affected if Android version is 12.0 (not 12.1, 12L, or later) since only 12.0 is listed as affected
  2. Identify apps with NotificationListenerService access
    Go to Settings > Apps > Special access > Notification access. Review the list of apps granted NotificationListenerService permission.
    Affected if Any app is listed with NotificationListenerService access granted
  3. Audit recently installed apps that request notification access
    Review recently installed applications, particularly those from unknown sources, that prompt for notification listener permissions.
    Affected if A recently installed or updated app has been granted notification listener permissions through a consent dialog
  4. Check for unexpected permission dialogs
    Review any recent permission consent dialogs that appeared with unfamiliar or misleading wording related to notifications or system access.
    Affected if User has granted any notification-related permissions through a dialog that seemed unclear or misleading

A device is affected if it runs Android 12.0 exactly AND has any app with NotificationListenerService permissions granted, particularly if the user granted access through a confusing consent dialog.

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

Apply the Android security patch for CVE-2021-1019 when released via system updates; users should exercise caution with unexpected permission dialogs.

Recommended fix Moderate confidence

Android 12.0 with January 2022 security patch level (or later monthly security update)

  1. Check current Android version and security patch level in Settings > About Phone > Android version
  2. Go to Settings > Security > Security update and ensure the January 2022 security patch or later is installed
  3. If not available through OTA, check with device manufacturer for the latest available security update for your specific device model
Caveat Standard update precautions apply - backup data before updating

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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