[Aikido] Fix 15 security issues in spring-core, spring-webmvc, spring-web and 6 more#314
Open
aikido-autofix[bot] wants to merge 1 commit into
Open
Conversation
There was a problem hiding this comment.
4 Open source vulnerabilities detected - medium severity
Aikido detected 4 vulnerabilities across 1 package, it includes 2 medium and 2 low vulnerabilities.
Details
Remediation Aikido suggests bumping the vulnerable packages to a safe version.
Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info
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 Spring and Jetty dependencies to fix open redirect/SSRF vulnerabilities in URL parsing, HTTP request smuggling, and XSS in JavaScript escaping.
✅ After thoroughly searching the codebase for all breaking changes mentioned in the Spring Core 5.3.20 => 5.3.49 and Kotlin stdlib 1.9.25 => 2.4.20 upgrades, no breaking changes were found that affect this codebase.
Spring Core Analysis:
No usage of
SimpleEvaluationContextfoundNo SpEL (Spring Expression Language) expressions found
No
@Valueannotations with SpEL expressions foundKotlin stdlib Analysis:
No open properties with backing fields requiring deferred initialization in init blocks
No expected/actual declarations (no Kotlin Multiplatform code)
No typealiases with upper bound violations
No SAM constructors with OptIn requirements
No suspend-marked anonymous functions in statement positions
No overrides of Java methods with raw-typed parameters using generic typed parameters
All data classes use constructor initialization (no deferred initialization issues)
All property declarations are properly initialized
The Kotlin code in this codebase uses standard patterns that are fully compatible with Kotlin 2.4.20.
All breaking changes by upgrading org.springframework:spring-core from version 5.3.20 to 6.2.11 (CHANGELOG)
SimpleEvaluationContextdoes not enforce read-only semantics (#33320) - This bug fix enforces read-only semantics that were previously not enforced, which may break code that was performing write operations.All breaking changes by upgrading org.jetbrains.kotlin:kotlin-stdlib from version 1.9.25 to 2.4.20 (CHANGELOG)
✅ 15 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