Repository navigation
feat(vulnerabilities): add additional severity indicators and improve layout - #20363
Merged
secustor merged 2 commits intoFeb 13, 2023
Merged
Conversation
viceice
approved these changes
Feb 13, 2023
Member
|
As we start to beautify this feature, do you have considered to move the CVEs in a nested collapsibale? The header should only show up if there are any and the first layer would be the current headlines. |
Collaborator
Author
Good suggestion. I already tried this but as always there are some constraints, e.g.:
I'll give the collapsing another try but not in this PR👍 |
secustor
approved these changes
Feb 13, 2023
secustor
enabled auto-merge (squash)
February 13, 2023 17:29
|
🎉 This PR is included in version 34.136.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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
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.
Changes
Refines the presentation of OSV-provided vulnerabilities:
affected.database_specific.cvss-> read it, if no CVSS information is given in the top-levelseverityfield.Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via:
Direct comparison:
Aliased mutable references from tls_rand & TlsWyRandPossible shell escape sequence injection vulnerability in Rack