Missing Authorization Affecting google-oauth-client-java package, versions <1.28.0-2


Severity

Recommended
0.0
critical
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.66% (80th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Missing Authorization vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIANUNSTABLE-GOOGLEOAUTHCLIENTJAVA-584453
  • published15 Jul 2020
  • disclosed9 Jul 2020

Introduced: 9 Jul 2020

CVE-2020-7692  (opens in a new tab)
CWE-862  (opens in a new tab)

How to fix?

Upgrade Debian:unstable google-oauth-client-java to version 1.28.0-2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream google-oauth-client-java package and not the google-oauth-client-java package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

CVSS Scores

version 3.1