dbcve.org
Google Play Services Software Development KitApplication · Google

CVE-2022-2390

HIGH · 8.4 CVSS v3.1 Published 2022-08-12
Fix available
A fix is available. Upgrade to 18.0.2 or later.
See remediation →
86/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
Apps developed with Google Play Services SDK incorrectly had the mutability flag set to PendingIntents that were passed to the Notification service. As Google Play services SDK is so widely used, this bug affects many applications. For an application affected, this bug will let the attacker, gain the access to all non-exported providers and/or gain the access to other providers the victim has permissions. We recommend upgrading to version 18.0.2 of the Play Service SDK as well as rebuilding and redeploying apps.

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

Google Play Services SDK incorrectly set the mutability flag on PendingIntents passed to the Notification service. This misconfiguration allows malicious actors to intercept or modify these PendingIntents, potentially granting unauthorized access to non-exported content providers and other protected components that the vulnerable application has permissions for.

MitigationUpgrade the Google Play Services SDK to version 18.0.2 or later, then rebuild and redeploy affected applications. Conduct a security review to verify no unauthorized access occurred during the vulnerability window.

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
Google Play Services Software Development KitApplication
Affected:< 18.0.2

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
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/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. Identify Google Play Services SDK version
    Examine your application's build configuration files (build.gradle, build.gradle.kts, or pom.xml for Android projects) and locate the com.google.android.gms:play-services-basement or related Play Services dependency. Check the version number specified.
    Affected if The listed version is below 18.0.2 (for example, 18.0.1, 18.0.0, or earlier)
  2. Verify notification code uses PendingIntents
    Search your application source code for imports of android.app.PendingIntent and usage with android.app.NotificationManager or android.support.v4.app.NotificationManager. Look for code that creates PendingIntent objects and passes them to notification builders via setContentIntent() or similar methods.
    Affected if Your application code creates PendingIntents and attaches them to notifications
  3. Review application permission declarations
    Inspect your AndroidManifest.xml file and look for permissions that grant access to protected components, particularly android.permission.READ_CONTACTS, android.permission.READ_SMS, or custom permissions protecting content providers declared with android:exported="false".
    Affected if The application declares permissions for non-exported content providers or other protected components that could be reached through a intercepted PendingIntent
  4. Check for exported content providers
    Review all <provider> elements in your AndroidManifest.xml. Identify those with android:exported="false" but which your notification-handling code or any component reachable via PendingIntent could theoretically access.
    Affected if The application has non-exported content providers that are accessible to components your notification PendingIntents can trigger

Your environment is affected if your application bundles a Google Play Services SDK version below 18.0.2 AND uses PendingIntents in notifications while holding permissions that could grant access to protected non-exported components.

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
Upgrade available Upgrade to 18.0.2 or later
Fixed in 18.0.2
Interim mitigation

Upgrade the Google Play Services SDK to version 18.0.2 or later, then rebuild and redeploy affected applications. Conduct a security review to verify no unauthorized access occurred during the vulnerability window.

Recommended fix High confidence

Google Play Services SDK 18.0.2

  1. Update the Google Play Services SDK dependency in your project to version 18.0.2 or later
  2. Rebuild the application with the updated SDK
  3. Redeploy the updated application to end users via the Google Play Store or other distribution channels

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

Fix this in Google Play Services Software Development Kit 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 the upgrade done

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-2022-2390 — 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-2022-2390 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