Hello, first of all: sorry for the delay in answering. It's being a busy time. second: thank you for your answers.
Now... On Tue, Jun 23, 2015 at 10:24 AM, Timo Pollmeier < [email protected]> wrote: > If you like, you can check here for presence: >> https://secinfo.greenbone.net >> If you don't find it there, then indeed a feed uptodateness issue is >> present. >> If you find it there, but not in your OpenVAS, check the publication date. >> > Thanks for the tip. I didn't know the website. > I agree with Jan here. The CVEs you listed should be in the feed already, > so it looks like there is something wrong with your local SCAP database. > > Assuming you are using SQLite as the database backend, you can try fixing > this by deleting the scap.db file (found in > "$PREFIX/var/lib/openvas/scap-data/", with "$PREFIX" being the prefix of > your OpenVAS installation) and running openvas-scapdata-sync again. > According to my local web app (GSA): OpenVAS SCAP Feed Version 201506240629 And the CVE is not present. So, again I try to update: /usr/local/sbin/openvas-scapdata-sync /usr/local/sbin/openvas-nvt-sync /usr/local/sbin/openvas-certdata-sync /usr/local/sbin/openvasmd/openvasmd --rebuild [restart] And again same version (201506240629) and the CVE not appearing. Then, as Timo suggested: rm /usr/local/var/lib/openvas/scap-data/scap.db /usr/local/sbin/openvas-scapdata-sync Again same version (201506240629) but this time the CVE is there !! Bingo! So, some questions arise: - Any clue why this could happen? - Any clue about how to detect there's a problem in the db (before discovering you are missing a CVE)? - It's a good policy to, once a month for example, delete scap.db and resync? Again, thank you Best Regards A.
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
