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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-2044 | 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. |
Github GHSA |
GHSA-f263-c949-w85g | Improper Authorization in Google OAuth Client |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: snyk
Published:
Updated: 2024-09-17T03:47:55.563Z
Reserved: 2020-01-21T00:00:00
Link: CVE-2020-7692
No data.
Status : Modified
Published: 2020-07-09T14:15:11.107
Modified: 2024-11-21T05:37:37.350
Link: CVE-2020-7692
OpenCVE Enrichment
No data.
EUVD
Github GHSA