dbcve.org
AndroidOperating system · Google

CVE-2021-39618

HIGH · 7.8 CVSS v3.1 Published 2022-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 multiple methods of EuiccNotificationManager.java, there is a possible way to install existing packages without user consent due to an unsafe PendingIntent. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-9Android ID: A-196855999

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

A local privilege escalation vulnerability in Android's EuiccNotificationManager allows an app with user execution privileges to install existing packages without user consent due to an unsafe PendingIntent. The PendingIntent is not properly secured, enabling a malicious application to intercept or trigger system actions that should require user confirmation.

MitigationApply the Android security patch for the appropriate build (Android 9-12) that addresses CVE-2021-39618. For organizations unable to patch immediately, monitor device behavior for suspicious package installation activity and restrict installation of apps from unknown sources.

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:= 9.0= 10.0= 11.0= 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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Check Android OS version
    Run 'getprop ro.build.version.release' in ADB shell or go to Settings > About Phone to view the Android version
    Affected if Version equals 9.0, 10.0, 11.0, or 12.0 exactly as listed in affected versions
  2. Verify EuiccNotificationManager component exists
    Run 'pm list packages -a | grep euicc' or 'dumpsys package com.android.euicc' in ADB shell to enumerate the EuiccNotificationManager system component
    Affected if The package com.android.euicc or related EuiccNotificationManager component is installed on the device
  3. Check for unsafe PendingIntent in EuiccService
    Analyze the EuiccNotificationManager APK or service definition for PendingIntent flags using 'dumpsys package -f com.android.euicc' to identify if the PendingIntent lacks FLAG_IMMUTABLE or proper intent validation
    Affected if The PendingIntent is exported or mutable, allowing a malicious app to intercept or trigger system actions
  4. Monitor for unauthorized package installations
    Review device logs via 'logcat -d | grep PackageInstaller' or check Settings > Apps > Package Installer for installation events that occurred without user confirmation prompt
    Affected if Package installations appear in logs or history that were not initiated through standard user confirmation dialogs

The device is affected if it runs Android version 9.0, 10.0, 11.0, or 12.0 and contains the EuiccNotificationManager component with the unsafe PendingIntent that can be intercepted to enable silent package installation without user consent.

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 the appropriate build (Android 9-12) that addresses CVE-2021-39618. For organizations unable to patch immediately, monitor device behavior for suspicious package installation activity and restrict installation of apps from unknown sources.

Recommended fix Moderate confidence

Android Security Patch Level 2022-01-05 or later (check device-specific availability)

  1. Check current Android security patch level: Go to Settings > About Phone > Security Patch Level
  2. Ensure your device has the latest available security update from your device manufacturer
  3. For Android 9.0, 10.0, 11.0, and 12.0 devices, contact the device manufacturer to confirm if a security update addressing CVE-2021-196855999 is available
  4. If no update is available from the manufacturer, consider upgrading to a newer Android version (Android 13+) which includes the security patch
Caveat Monthly security updates are device-specific; not all devices receive updates; some older devices may not receive patches for this vulnerability

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

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-2021-39618 — 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-39618 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