This repository has been archived by the owner on Oct 14, 2024. It is now read-only.
fix(scanner): enrich vulnerability data instead of using first vulnerability #1971
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
paralta
added
bug
paralta
changed the title
paralta
force-pushed
the
inconsistent-vulnerability-fix
branch
from
7dd5d97 to
b6e663a
Compare
paralta
force-pushed
the
inconsistent-vulnerability-fix
branch
from
b6e663a to
771f40d
Compare
ramizpolic
reviewed
Aug 1, 2024
ramizpolic
reviewed
Aug 1, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Currently, we use the first vulnerability in merged vulnerabilities results
vmclarity/cli/presenter/apimodel.go
Line 72 in fb54c41
These code changes allow us to merge vulnerabilities with the same ID into a single vulnerability by enriching the vulnerability data with the data from all the different entries.
Type of Change
Checklist