Com.Google.Oauth Client
Approved changes feed: RSS · Atom
cpe:2.3:a:n/a:com.google.oauth-client:google-oauth-client:*:*:*:*:*:*:*:*
part: a version: google-oauth-client update: *
| Vendor | N/A (22f567d3-1203-528c-8f0e-3eb9c2f6ca78) |
|---|---|
| Product | Com.Google.Oauth Client (79035b0f-6170-588e-b178-2b276e1dcca4) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-7692 |
vulnerable | 2026-06-08 05:27:13.979511 |
Improper Authorization
HIGH (7.4)
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.
Published: 2020-07-09T13:20:16.446Z
Updated: 2024-09-17T03:47:55.563Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.