Skip to content

Google Play Services SDK leads to apps having incorrectly set mutability flag

Moderate severity GitHub Reviewed Published Aug 13, 2022 to the GitHub Advisory Database • Updated Jan 30, 2023

Package

maven com.google.android.gms:play-services-basement (Maven)

Affected versions

< 18.0.2

Patched versions

18.0.2

Description

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.

References

Published by the National Vulnerability Database Aug 12, 2022
Published to the GitHub Advisory Database Aug 13, 2022
Reviewed Aug 18, 2022
Last updated Jan 30, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N

EPSS score

0.044%
(15th percentile)

Weaknesses

CVE ID

CVE-2022-2390

GHSA ID

GHSA-cm6r-892j-jv2g

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.