[Aikido] Fix 6 security issues in jetty-server, jetty-http, kotlin-stdlib#315
Open
aikido-autofix[bot] wants to merge 1 commit into
Open
[Aikido] Fix 6 security issues in jetty-server, jetty-http, kotlin-stdlib#315aikido-autofix[bot] wants to merge 1 commit into
aikido-autofix[bot] wants to merge 1 commit into
Conversation
This file contains hidden or 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
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.
Upgrade Jetty and Kotlin to fix HTTP request smuggling via chunk extensions, URI parsing bypass vulnerabilities, ThreadLimitHandler DoS, and unsafe deserialization RCE.
✅ After thoroughly analyzing the codebase for patterns related to all breaking changes in the Kotlin stdlib upgrade from 1.9.25 to 2.4.20, no breaking changes affect this codebase.
The codebase contains:
Simple data classes with immutable properties (no open properties with backing fields requiring deferred initialization)
Standard override methods that don't involve raw types or generic type conflicts
No Kotlin Multiplatform code (no
expect/actualdeclarations)No
@OptInannotations or experimental API usageNo
typealiasdeclarationsNo suspend anonymous functions in statement positions
Lambda expressions used in standard library functions (
.use,.also,.apply) which are not affected by the breaking changesAll Kotlin code follows standard patterns that are compatible with Kotlin 2.4.20.
All breaking changes by upgrading org.jetbrains.kotlin:kotlin-stdlib from version 1.9.25 to 2.4.20 (CHANGELOG)
✅ 6 CVEs resolved by this upgrade
This PR will resolve the following CVEs:
2.4.20code execution is possible via unsafe deserialization in the build cache metadata.🔗 Related Tasks