CVE-2020-7692 (High) detected in google-oauth-client-1.25.0.jar - autoclosed

[mend-for-github-com]

CVE-2020-7692 - High Severity Vulnerability

Vulnerable Library - google-oauth-client-1.25.0.jar

Google OAuth Client Library for Java. Functionality that works on all supported Java platforms, including Java 5 (or higher) desktop (SE) and web (EE), Android, and Google App Engine.

Library home page: https://github.com/google/google-oauth-java-client

Path to dependency file: testdroid-api/pom.xml

Path to vulnerable library: canner/.m2/repository/com/google/oauth-client/google-oauth-client/1.25.0/google-oauth-client-1.25.0.jar

Dependency Hierarchy:

• ❌ google-oauth-client-1.25.0.jar (Vulnerable Library)

Found in HEAD commit: e27a23c3fc46b3858353a24f6550013c097bb0c4

Found in base branch: master

Vulnerability Details

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.

Publish Date: 2020-07-09

URL: CVE-2020-7692

CVSS 3 Score Details (9.1)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: googleapis/google-oauth-java-client#470

Release Date: 2020-07-09

Fix Resolution: com.google.oauth-client:google-oauth-client:1.31.0

---

⛑️ Automatic Remediation is available for this issue

[mend-for-github-com]

✔️ This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.