osv: parse database_specific severity when no CVSS severity is defined #1294
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
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1294 +/- ##
==========================================
+ Coverage 55.33% 55.84% +0.50%
==========================================
Files 265 265
Lines 16574 16597 +23
==========================================
+ Hits 9172 9268 +96
+ Misses 6451 6366 -85
- Partials 951 963 +12 ☔ View full report in Codecov by Sentry. |
Occasionally there are OSV advisories that don't include any severity information in the `.severity` object but they do contain a severity in the `.database_specific` object. This change attempts to parse that severity if we don't get a severity from the native `.severity` object. Signed-off-by: crozzy <joseph.crosland@gmail.com>
crozzy
force-pushed
the
crozzy-parse-db-specific-osv
branch
from
0000426
to
fed6af8
Compare
github-actions
bot
removed
the
needs-changelog
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.
Occasionally there are OSV advisories that don't include any severity information in the
.severityobject but they do contain a severity in the.database_specificobject. This change attempts to parse that severity if we don't get a severity from the native.severityobject.