vulnerabilities: update nvdcve file name

The filename is outdated as its version was already bumped and there are
also different files for different feed choices.
Use glob to match any available file.

Also the directory changed to CVE_CHECK2 meanwhile, so Update it, too.

(From yocto-docs rev: 1b4d559ad5489a34cec26f9aad2687d2cb3ecc0a)

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
(cherry picked from commit a2f18cb23183401d9d8e2fd4499d164ef8d86e44)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
This commit is contained in:
Peter Marko 2025-08-24 16:53:16 +02:00 committed by Steve Sakoman
parent 8150b2ba7c
commit 7ec60228eb

View File

@ -318,7 +318,7 @@ products defined in :term:`CVE_PRODUCT`. Then, for each found CVE:
The CVE database is stored in :term:`DL_DIR` and can be inspected using
``sqlite3`` command as follows::
sqlite3 downloads/CVE_CHECK/nvdcve_1.1.db .dump | grep CVE-2021-37462
sqlite3 downloads/CVE_CHECK2/nvd*.db .dump | grep CVE-2021-37462
When analyzing CVEs, it is recommended to: