CVE-2014-7922: n/a vulnerability

CVE-2014-7922: The GoogleAuthUtil.getToken method in the Google Play services SDK before 2015 sets parameters in OAuth tok...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 13:03 UTC (UTC+00:00)

Security readout for executives and security teams

A malicious Android app could abuse old Google Play services SDK token handling to bypass the expected consent dialog and obtain Google account tokens for unintended scopes. The described impact includes sensitive SID and LSID scopes and potential account access. This is a historical issue published in 2015; the supplied sources do not show active exploitation. Likely exposure is Android applications built against Google Play services SDK before 2015 that call GoogleAuthUtil.getToken with attacker-influenced Bundle extras or permissive token request handling. Treat as high priority only for legacy Android estates or archived apps still distributed to users. Modern apps rebuilt on supported SDKs are less likely to be exposed, but confirm through dependency inventory. Mitigation focus: Inventory Android apps and libraries using Google Play services SDK before 2015.; Rebuild affected apps with a current supported Google Play services SDK.; Review OAuth scope requests and remove unnecessary sensitive or legacy scopes..

Prepared: Jun 13, 2026, 22:56 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2014-7922 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Feb 23, 2015, 02:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://gist.github.com/isciurus/df4d7edd9c3efb4a0753CVE reference · x_refsource_MISC

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.