Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: use correct types for modifiedSubAvailabilityImpact, modifiedSubIntegrityImpact, and modifiedSubConfidentialityImpact #274

Merged
merged 1 commit into from
Feb 16, 2025

Conversation

jeremylong
Copy link
Owner

Incorrectly used the wrong type for three fields that are rarely filled out in the NVD data. This resolves #270

@marcelstoer thanks for suggesting adding the test case via #272 - I've included that here.

@jeremylong
Copy link
Owner Author

@aikebah or @marcelstoer does this look good to you?

@aikebah
Copy link

aikebah commented Feb 16, 2025

LGTM

@jeremylong jeremylong merged commit e32abd5 into main Feb 16, 2025
2 checks passed
@marcelstoer
Copy link
Contributor

I expect this leading to an ODC 12.0.3 release but are you also going to release a new v11 including this fix? (haven't figured out yet what was breaking in between)

@aikebah
Copy link

aikebah commented Feb 16, 2025

@marcelstoer the only breaking change to my knowledge was the extension of the reports with CVSSv4 data given that we've seen in past that reports are post-processed by various users to compose the information into their own dashboarding and adding CVSSv4 data is likely to break those pipelines. IIRC that was the only reason for the new major

jeremylong/DependencyCheck#7204

@jeremylong
Copy link
Owner Author

@marcelstoer is there a need to release a new v11? We've generally just required the upgrade to the latest.

@aikebah
Copy link

aikebah commented Feb 16, 2025

@jeremylong Might be good to retroactively indicate in the changelog that the addition of CVSS v4 in the reports is the 'breaking' change that warranted the new major for v12.0.0. My impresson is that then just releasing a new v12 would be sufficient and people will mostly be fine to onboard on v12.x.
New majors are typically a reason for caution in upgrading, especially if the reasoning for a new major is not clear from the changelog.

@marcelstoer
Copy link
Contributor

@jeremylong thanks for amending the changelog for 12.0.

@aikebah thanks for insights.

New majors are typically a reason for caution in upgrading, especially if the reasoning for a new major is not clear from the changelog.

Yep, that is exactly why I haven't upgraded yet. If I update our pipeline at work, 100+ projects are going to be affected all at once. Due to this issue, I'll now expedite the upgrade 😄

@jeremylong
Copy link
Owner Author

@marcelstoer sorry for not highlighting the breaking change earlier. I'll try to do better in the future ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Download from NVD is broken again
3 participants