First published: Fri Jul 03 2020(Updated: )
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.
Credit: report@snyk.io
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/jenkins | <2-plugins-0:4.13.1684911916-1.el8 | 2-plugins-0:4.13.1684911916-1.el8 |
redhat/jenkins | <2-plugins-0:4.10.1675144701-1.el8 | 2-plugins-0:4.10.1675144701-1.el8 |
redhat/jenkins | <2-plugins-0:4.9.1675668922-1.el8 | 2-plugins-0:4.9.1675668922-1.el8 |
redhat/google-oauth-client | <1.31.0 | 1.31.0 |
Google OAuth Client Library for Java | <1.31.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2020-7692 has a high severity rating due to the lack of proper PKCE implementation which may expose sensitive data.
To resolve CVE-2020-7692, update the vulnerable packages to the recommended versions: google-oauth-client to 1.31.0 and Jenkins plugins to 4.13.1684911916-1.el8, 4.10.1675144701-1.el8, or 4.9.1675668922-1.el8.
CVE-2020-7692 affects the google-oauth-client library and multiple versions of Jenkins plugins.
The main issue with CVE-2020-7692 is that the PKCE support for OAuth 2.0 is not implemented as per the standard, leading to potential security vulnerabilities.
Yes, CVE-2020-7692 is considered a client-side vulnerability due to its impact on native applications utilizing OAuth 2.0.