CVE-2020-7692

CVE-2020-7692 is a high-severity missing authorization vulnerability in com.google.oauth-client:google-oauth-client (maven), affecting versions < 1.31.0. It is fixed in 1.31.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Improper Authorization in Google OAuth Client

PKCE support is not implemented in accordance with the RFC for OAuth 2.0 for Native Apps. Without the use of PKCE, the authorization code returned by an authorization server is not enough to guarantee that the client that issued the initial authorization request is the one that will be authorized. An attacker is able to obtain the authorization code using a malicious app on the client-side and use it to gain authorization to the protected resource. This affects the package com.google.oauth-client:google-oauth-client before 1.31.0.

Impact

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2020-7692 has a CVSS score of 7.4 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.31.0); upgrading removes the vulnerable code path.

Affected versions

com.google.oauth-client:google-oauth-client (< 1.31.0)

Security releases

com.google.oauth-client:google-oauth-client → 1.31.0 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade com.google.oauth-client:google-oauth-client to 1.31.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2020-7692? CVE-2020-7692 is a high-severity missing authorization vulnerability in com.google.oauth-client:google-oauth-client (maven), affecting versions < 1.31.0. It is fixed in 1.31.0. The application does not perform an authorization check before performing a sensitive operation.
  2. How severe is CVE-2020-7692? CVE-2020-7692 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of com.google.oauth-client:google-oauth-client are affected by CVE-2020-7692? com.google.oauth-client:google-oauth-client (maven) versions < 1.31.0 is affected.
  4. Is there a fix for CVE-2020-7692? Yes. CVE-2020-7692 is fixed in 1.31.0. Upgrade to this version or later.
  5. Is CVE-2020-7692 exploitable, and should I be worried? Whether CVE-2020-7692 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2020-7692 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2020-7692? Upgrade com.google.oauth-client:google-oauth-client to 1.31.0 or later.

Other vulnerabilities in com.google.oauth-client:google-oauth-client

Stop the waste.
Protect your environment with Kodem.