Bump Scala to >2.13.9 to fix CVE #382
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fredex42
reviewed
Mar 14, 2023
fredex42
force-pushed
the
pt/bump-scala-to-2.13.9
branch
from
38bddcc to
621e992
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this change?
Bumps Scala to >2.13.9 to fix CVE.
Content-api-client-default is causing the okhttp vulnerability in the new Snyk report: https://app.snyk.io/org/guardian/project/8ecf100e-b5f7-43e5-bbaa-c28fcd28eb7a/history/c3017eca-b17a-4035-88f0-e7a02aa46b43 - In order to fix okhttp, content-api-client-default has to be bumped.
However, all the content-api-client-default releases have CVE-2022-36944 - this is not flagged by Snyk, but Maven: https://mvnrepository.com/artifact/com.gu/content-api-client-default_2.13 e.g. https://mvnrepository.com/artifact/com.gu/content-api-client-default_2.13/19.2.1
How to test
TBD
How can we measure success?
Have we considered potential risks?
Images
Accessibility