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.

Sign up for GitHub

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

Jump to bottom

The sort of top 5 dangerous CVEs #19014

Closed
chlins opened this issue Jul 26, 2023 · 0 comments · Fixed by #19103
Closed

The sort of top 5 dangerous CVEs #19014

chlins opened this issue Jul 26, 2023 · 0 comments · Fixed by #19103
Assignees
@stonezdj @AllForNothing
Labels
target/2.9.0

Comments

@chlins
Copy link
Member

chlins commented Jul 26, 2023

How can we help you?

The Critical CVE should on top of High when they with the same score.

image
stonezdj pushed a commit to stonezdj/harbor that referenced this issue Aug 4, 2023
Sort most dangerous vulnerabilities by score and severity level
b45b7d1 
  Check it is referred by a scan_report
  Add index to report_vulnerability_record to improve performance
  Fixes goharbor#19014 goharbor#19028

Signed-off-by: stonezdj <daojunz@vmware.com>
@stonezdj stonezdj mentioned this issue Aug 4, 2023
Merged
5 tasks
stonezdj pushed a commit to stonezdj/harbor that referenced this issue Aug 4, 2023
Sort most dangerous vulnerabilities by score and severity level
6d90e3d 
  Check it is referred by a scan_report
  Add index to report_vulnerability_record to improve performance
  Fixes goharbor#19014 goharbor#19028

Signed-off-by: stonezdj <daojunz@vmware.com>
stonezdj pushed a commit to stonezdj/harbor that referenced this issue Aug 6, 2023
Sort most dangerous vulnerabilities by score and severity level
a033bf4 
  Check it is referred by a scan_report
  Add index to report_vulnerability_record to improve performance
  Fixes goharbor#19014 goharbor#19028

Signed-off-by: stonezdj <daojunz@vmware.com>
stonezdj pushed a commit to stonezdj/harbor that referenced this issue Aug 7, 2023
@stonezdj
Sort most dangerous vulnerabilities by score and severity level
b435b4b 
  Check it is referred by a scan_report
  Add index to report_vulnerability_record to improve performance
  Fixes goharbor#19014 goharbor#19028

Signed-off-by: stonezdj <daojunz@vmware.com>
stonezdj pushed a commit to stonezdj/harbor that referenced this issue Aug 7, 2023
@stonezdj
Sort most dangerous vulnerabilities by score and severity level
dede4ba 
  Check it is referred by a scan_report
  Add index to report_vulnerability_record to improve performance
  Fixes goharbor#19014 goharbor#19028

Signed-off-by: stonezdj <daojunz@vmware.com>
stonezdj added a commit that referenced this issue Aug 7, 2023
@stonezdj
Sort most dangerous vulnerabilities by score and severity level (#19103)
0e92eae 
Check it is referred by a scan_report
  Add index to report_vulnerability_record to improve performance
  Fixes #19014 #19028

Signed-off-by: stonezdj <daojunz@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stonezdj stonezdj

@AllForNothing AllForNothing

Labels
target/2.9.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Sort most dangerous vulnerabilities by score and severity level stonezdj/harbor
3 participants
@stonezdj @AllForNothing @chlins