-
Notifications
You must be signed in to change notification settings - Fork 19
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
Why all vulnerabilities under Advisories has "NONE" as severity? #278
Comments
Indeed |
Did yesterday PR fix this or still open? |
@bobmcwhirter It is still a problem. How to reproduce it:
{
"items": [
{
"identifier": "CVE-2023-20862",
"sha256": "e6a2bc1084c77809af965dc4facb0c28aca67210f054eb8de4778190b8c6347e",
"issuer": {
"id": 1,
"name": "Red Hat Product Security",
"cpe_key": null,
"website": null
},
"published": "2023-04-19T00:00:00Z",
"modified": "2023-11-14T22:09:12Z",
"title": "spring-security: Empty SecurityContext Is Not Properly Saved Upon Logout",
"average_severity": null,
"average_score": null,
"vulnerabilities": [
{
"identifier": "CVE-2023-20862",
"severity": "none",
"score": 0.0
}
]
}
],
"total": 1
} You can see that the |
Ah, so our CSAF ingestor seems to not be ingesting scores. |
Fixes: trustification#278 Ported test over from OSV's loader, but commented out quite a bit since the ingestion of the product statuses seems incomplete. Signed-off-by: Jim Crossley <jim@crossleys.org>
Fixes: #278 Ported test over from OSV's loader, but commented out quite a bit since the ingestion of the product statuses seems incomplete. Signed-off-by: Jim Crossley <jim@crossleys.org>
GET /api/v1/advisory
returns something like:I noticed that ALL vulnerabilities under the Advisory entity has
none
asseverity
. Is it just a coincidence that we don't have other type of severity? I mean, all Red Hat CSAF files we currently import have "none" as severity? If so, that is fine, it just look suspicious.I got the impression that the v1 of Trustification didn't even have a single "none" as severity.
I wouldn't consider this as a bug, yet. If anyone can confirm the current "none" severity are actually correct, we can close this issue.
The text was updated successfully, but these errors were encountered: