Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-7692

Vulnerability in com.google.oauth-client:google-oauth-client (CVE-2020-7692)

Summary

Vulnerability in com.google.oauth-client:google-oauth-client (CVE-2020-7692). Confidential information can be exposed externally. Mitigation: upgrade to 1.31.0 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-7692 has been found in com.google.oauth-client:google-oauth-client.
Confidential information can be exposed externally.
What to do: upgrade com.google.oauth-client:google-oauth-client to 1.31.0 or later.
If unsure, ask your IT team or search "com.google.oauth-client:google-oauth-client CVE-2020-7692" on the vendor's site.

CVE-2020-7692 (com.google.oauth-client:google-oauth-client) — CWE-862
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.31.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-862) exists in com.google.oauth-client:google-oauth-client.

📍 Affected scope

Check the vendor advisory for the affected versions of com.google.oauth-client:google-oauth-client.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 1.31.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで com.google.oauth-client:google-oauth-client を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade com.google.oauth-client:google-oauth-client to 1.31.0

    ステージング環境で 1.31.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven com.google.oauth-client:google-oauth-client
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.31.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details