Resolving google-oauth and jetty-io vulnerability #24120
+22
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Identified security vulnerability issues of severity high from jetty-io-9.4.14.v20181114.jar 1.31.2.jar and resolved the same.
Excluded the transitive dependency of jetty-io occuring from parent packages that does not break the build or impact the functionality but removes the said exploitable.
Identified security vulnerability issue of severity high from google-oauth-client-1.31.2.jar and resolved the same.
Excluded the transitive dependency of google-oauth-client occuring from parent package google-cloud-bigquerystorage that does not break the build or impact the functionality but resolves the said exploitable.
Motivation and Context
Direct vulnerabilities:
CVE-2021-28165
CVE-2021-22573
Impact
Eclipse Jetty is vulnerable to a denial of service, caused by improper input validation. By sending a specially-crafted TLS frame, a remote attacker could exploit this vulnerability to cause CPU resources to reach to 100% usage.
Google APIs google-oauth-java-client could allow a remote attacker to bypass security restrictions, caused by no PKCE support implemented. By executing a specially-crafted application, an attacker could exploit this vulnerability to obtain the authorization code, and gain authorization to the protected resource.
Test Plan
Contributor checklist
Release Notes
Please follow release notes guidelines and fill in the release notes below.