Fixed: severity filter uses vulnerability severity instead of finding severity #99
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
…gGroup (aka Query) severity.
olgakil
approved these changes
Mar 2, 2021
james-bostock-cx
pushed a commit
to james-bostock-cx/checkmarx-spring-boot-java-sdk
that referenced
this pull request
Mar 18, 2021
R&D changes related to Common client
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.
By default, finding severity is the same as the severity of its vulnerability type. However, users are able to override severity for a specific finding.
Before the fix, filtering logic used the severity of vulnerability type. This could lead to incorrect results if a user overrode severity for specific findings.
Work item: 531.
The tests are in CxFlow.