Skip to content

fix: references to cvssv2 and cvssv3 fields in json and xml reports#6212

Merged
jeremylong merged 6 commits intodependency-check:mainfrom
clayton-piscopo:patch-1
Dec 4, 2023
Merged

fix: references to cvssv2 and cvssv3 fields in json and xml reports#6212
jeremylong merged 6 commits intodependency-check:mainfrom
clayton-piscopo:patch-1

Conversation

@clayton-piscopo
Copy link
Copy Markdown
Contributor

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

fixed reference to exploitabilityScore and impactScore for cvssV2 and cvssV3
bumped to next version
fixed reference to exploitabilityScore and impactScore
@boring-cyborg boring-cyborg Bot added the core changes to core label Dec 4, 2023
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 clayton-piscopo changed the title Patch 1 fix: references to cvssv2 and cvssv3 fields in json and xml reports Dec 4, 2023
@jeremylong
Copy link
Copy Markdown
Collaborator

Thank you for the PR. Sorry for the mistake.

Comment thread pom.xml Outdated
@jeremylong
Copy link
Copy Markdown
Collaborator

I'll correct the pom version in another PR. not sure what happened - but it looks like I messed up a merge recently.

@jeremylong jeremylong added this to the 9.0.3 milestone Dec 4, 2023
@jeremylong jeremylong merged commit 629adb8 into dependency-check:main Dec 4, 2023
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Dec 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

core changes to core

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants