Skip to content

Commit

Permalink
Fix: Use severity column in CVEs alert iterators
Browse files Browse the repository at this point in the history
The iterators in the new_cves_list function used by new / updated CVE
alerts now use the correct severity column.

Before the use of the incorrect column caused the alerts to fail.
  • Loading branch information
timopollmeier committed Apr 25, 2023
1 parent 39fabc0 commit 8c0bfb0
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions src/manage_sql.c
Original file line number Diff line number Diff line change
Expand Up @@ -33292,11 +33292,11 @@ new_cves_list (event_t event, const void* event_data, alert_t alert,
count = 0;
if (example)
init_iterator (&rows,
"SELECT uuid, name, cvss, description FROM cves"
"SELECT uuid, name, severity, description FROM cves"
" LIMIT 4;");
else if (event == EVENT_NEW_SECINFO)
init_iterator (&rows,
"SELECT uuid, name, cvss, description FROM cves"
"SELECT uuid, name, severity, description FROM cves"
" WHERE creation_time"
" > coalesce (CAST ((SELECT value FROM meta"
" WHERE name"
Expand All @@ -33306,7 +33306,7 @@ new_cves_list (event_t event, const void* event_data, alert_t alert,
" ORDER BY creation_time DESC;");
else
init_iterator (&rows,
"SELECT uuid, name, cvss, description FROM cves"
"SELECT uuid, name, severity, description FROM cves"
" WHERE modification_time"
" > coalesce (CAST ((SELECT value FROM meta"
" WHERE name"
Expand Down

0 comments on commit 8c0bfb0

Please sign in to comment.