Bump okhttp version to 4.12.0 to resolve CVE-2023-3635, CVE-2022-24329 #81
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
Upgrade okhttp dependency from 4.10.0 to 4.12.0 in order to resolve vulnerabilities present in transient dependency okio.
CVE-2023-3635: Older versions of okio's GzipSource.kt contain a vulnerability that may allow attackers to execute denial of service attacks. This vulnerability is present in okio versions starting at 2.0.0, patched in 3.4.0. Duo-client currently leverages okhttp version 4.10.10, which includes okio version 3.0.0 as a dependency.
CVE-2022-24329: Older versions of okio and okhttp also include as dependencies kotlin-stdlib-jdk8 version 1.5.31 and kotlin-stdlib-common version 1.5.31, which are vulnerable to improper locking.
Both of these vulnerabilities can be resolved by upgrading okhttp from 4.10.0 to 4.12.0.
Current dependency tree:
Dependency tree with patch applied:
Motivation and Context
Patches open vulnerabilities with one minor version increment.
How Has This Been Tested?
Ran
mvn test
locally. 10 passed, 11 failed:Types of Changes