Checkmarx AI Remediation - CVE-2020-1757#11
Open
juegge wants to merge 1 commit into
Open
Conversation
Open
Contributor
Author
|
Fixed Issues (36)
Great job! The following issues were fixed in this Pull Request
Use @Checkmarx to interact with Checkmarx PR Assistant. |
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.




Checkmarx One – Remediation
CVE-2020-1757 ·
High
Triage context:
Reachable ·
Exploitable
Fix CVE-2020-1757 path normalization vulnerability in undertow-core
What is the issue?
CVE-2020-1757 is a HIGH severity vulnerability in undertow-core versions prior to 2.0.30.SP1 and 2.1.0.Final that incorrectly normalizes servlet paths by truncating after semicolons. This path normalization flaw allows attackers to bypass security constraints and access unauthorized resources through malformed URL paths containing semicolons, exploiting improper input validation (CWE-20).
Why should it be fixed?
This vulnerability poses a significant security risk with a network attack vector and low attack complexity, making it easily exploitable remotely. Successful exploitation could lead to unauthorized access to sensitive data and protected application endpoints. The application actively uses undertow's AJP protocol classes, directly exposing it to path manipulation attacks.
How should it be fixed?
Upgrading undertow-core from version 2.0.9.Final to 2.2.39.Final in pom.xml. This version includes security patches that fix the path normalization logic to properly handle semicolons in servlet paths. Running mvn dependency:resolve to ensure Maven's dependency resolution is updated and the new version is properly locked. No application code changes are required as the upgrade maintains backward compatibility with existing undertow class usage.
Use @Checkmarx to interact with Checkmarx PR Assistant.
Examples:
@Checkmarx how are you able to help me?@Checkmarx rescan this PR