fix: references to cvssv2 and cvssv3 fields in json and xml reports #6212
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
fixed reference to exploitabilityScore and impactScore for cvssV2 and cvssV3
bumped to next version
fixed reference to exploitabilityScore and impactScore
fixed reference to fields which are available in CvssV2 and not CvssV2.cvssData
fixed references to CvssV2 which were mistakenly pointing to CvssV2.cvssData
clayton-piscopo
changed the title
jeremylong
approved these changes
Dec 4, 2023
|
Thank you for the PR. Sorry for the mistake. |
jeremylong
reviewed
Dec 4, 2023
|
I'll correct the pom version in another PR. not sure what happened - but it looks like I messed up a merge recently. |
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.
Fixes Issue
#6210
Description of Change
updated references to exploitabilityScore and impactScore fields for CvssV2 and CvssV3 in json and xml reports.
Have test cases been added to cover the new functionality?
no