-
-
Notifications
You must be signed in to change notification settings - Fork 582
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
Vuln db severity #3595
Vuln db severity #3595
Conversation
Apparently the severity was never added to those vulnerabilities. use setSeverity to fix this issue. Signed-off-by: Andres Tito <[email protected]>
Signed-off-by: Andres Tito <[email protected]>
src/main/java/org/dependencytrack/tasks/metrics/ComponentMetricsUpdateTask.java
Outdated
Show resolved
Hide resolved
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferencesYou may notice some variations in coverage metrics with the latest Coverage engine update. For more details, visit the documentation |
Signed-off-by: Andres Tito <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @LaVibeX!
Description
Severity not added to VulnDB vulnerabilities. use setSeverity to fix this issue.
Addressed Issue
Fixes #3589
Additional Details
Add an explicit null check and a Logger WARN message in case Vulnerability Severity is null.
Checklist