Hello GVM team, first, thanks for your great work.
I’ve been using GVM for a long period in Kali. Today, I upgraded the kali platform and the migration to the latest version of GVM and it seems to have a problem regenerating the postgres tables of the CVEs and CPEs databases, because no item appears under Security Information, while NVTs, or CERTs info seems to be fully populated.
The installation and the applications works well, but when I check the output of any report about CVE it says " The CVE you were looking for could not be found.". It does the same for CPEs…
Can you help me to understand what I am missing and how to solve it? I read that there are some problems with NIST and the publication of the CVE and CPE original databases, but in the scap directory there are a lot of jsons with all the CVEs and one with the CPEs…
Yes, I did it, but, -despite it works and updates the cert advisories and NVTs- it does not create the data of CVEs nor CPEs under the scap schema of the postgres database…
I’ve been able to install and use the scap-download, but it does not populate the right tables of the database…
Hi, Eero. I reinstalled gmv-openvas all packages in a kali rolling 2025, recently updated, changing old gmvd database to gmvd-old and everything happened again (the system works, but there is no CVE or CPE data in the app, nor in the database, under scap schema).
Of course, I used gvm-setup, gvm-check-setup and greenbone-feed-sync to test everything else looks and works fine.
I managed to install and test the greenbone-scap script to download NIST cves and cpes into the database, hoping it would be updating the gvmd scap schema, but it doesn’t.
Please, let me know if you would need any more info to track the issue.
Just in case it can be of help to understand the problem, I have been comparing the databases of the last version of the openvas app in kali with the previous one.
What I can see is differences in scap schema tables. The new version has all tables empty except one: meta. This meta table has the following data in last version: database_version=22, last_update=1746748800. The previous version is the version from which I updated openvas and had the following data in meta table: database_version=21, last_update=1726099200.
The scap schema in the database_version 21 had the following tables: affected_products, cpe_details, cpes, cves, epss_scores, meta. All of them, populated. But the scap schema in the database_version 22 has the following tables empty: affected_products, cpe_details, cpe_match_nodes, cpe_match_strings, cpe_matches, cpe_nodes_match_criteria, cpe_refs, cpes, cpes_deprecated_by, cve_references, cves and epss_scores. The last table, meta, is populated with the previous mentioned data.
Thanks again. As I said before, I tried the installation of the new version two times with the new kali rolling 2025: one updating and one installing from zero, with the same results: no information about CVEs and CPEs,
Hi @Eero and @babyboy33, I think I found the problem: there was not enough free space for users in the main disk of Kali, where the database and root filesystem reside.
Now it is syncing data and seems it has automagically made a new schema named scap2 with the same type of info… Maybe I can delete it in the future?