fix: update CVE's severity and store multiple same CVE's in multiple packages #5168
Conversation
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
…-store table and handling backward compatibility
prakash100198
requested review from
prakarsh-dt,
vikramdevtron,
kripanshdevtron and
nishant-d
as code owners
github-actions
bot
added
PR:Ready-to-Review
and removed
PR:Issue-verification-failed
labels
prakash100198
changed the title
subhashish-devtron
approved these changes
Jun 3, 2024
nishant-d
approved these changes
Jun 3, 2024
|
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.
Description
This pr fixes the issue where the cve's severity are not updated and if one package contains multiple CVEs then we don't store them in the db.
Fixes #4972
Checklist:
Does this PR introduce a user-facing change?