Google Play Services DSK up to 6.0 has_permission=1 access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Google Play Services DSK up to 6.0 and classified as critical. Affected by this issue is some unknown functionality of the component Services. The manipulation of the argument has_permission=1 leads to access control. This vulnerability is listed as CVE-2014-7922. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability was found in Google Play Services DSK up to 6.0 and classified as critical. This issue affects an unknown part of the component Services. The manipulation of the argument has_permission=1 with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is integrity. The summary by CVE is:
The GoogleAuthUtil.getToken method in the Google Play services SDK before 2015 sets parameters in OAuth token requests upon finding a corresponding _opt_ parameter in the Bundle extras argument, which allows attackers to bypass an intended consent dialog and retrieve tokens for arbitrary OAuth scopes including the SID and LSID scopes, and consequently obtain access to a Google account, via a crafted application, as demonstrated by setting the has_permission=1 parameter value upon finding _opt_has_permission in that argument.
The weakness was presented 02/22/2015 (Website). The advisory is shared at gist.github.com. The identification of this vulnerability is CVE-2014-7922 since 10/06/2014. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 6.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Vulnerability Center (SBV-52346†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Play Services DSK 6.1
Timeline
10/06/2014 🔍02/22/2015 🔍
02/22/2015 🔍
02/22/2015 🔍
03/30/2015 🔍
08/27/2015 🔍
11/14/2017 🔍
Sources
Vendor: google.comAdvisory: gist.github.com
Status: Not defined
CVE: CVE-2014-7922 (🔍)
GCVE (CVE): GCVE-0-2014-7922
GCVE (VulDB): GCVE-100-74273
Vulnerability Center: 52346 - Google Play Services SDK Remote Bypass of Google Account Access Mechanism, Medium
Entry
Created: 03/30/2015 12:19Updated: 11/14/2017 08:02
Changes: 03/30/2015 12:19 (47), 11/14/2017 08:02 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.