Closed philroche closed 2 months ago
Hi @philroche thanks for the report. I'm taking a look now.
@willmurphyscode Thank you. The latest grype db published today has no checksum issue.
➜ 20240822-grype-db-issues grype db delete && grype db update
Vulnerability database deleted
✔ Vulnerability DB [updated]
Vulnerability database updated to latest version!
➜ 20240822-grype-db-issues grype db list | head -n 3
Built: 2024-08-23 01:31:27 +0000 UTC
URL: https://grype.anchore.io/databases/vulnerability-db_v5_2024-08-23T01:31:27Z_1724386835.tar.gz
Checksum: sha256:d8b31c95d998c89f4664a2f318ad727bb45c8a2c918a3dddd8196afd985e5db1
➜ 20240822-grype-db-issues wget -q -O db.tar.gz "https://grype.anchore.io/databases/vulnerability-db_v5_2024-08-23T01:31:27Z_1724386835.tar.gz"
➜ 20240822-grype-db-issues tar --extract --ungzip --file "db.tar.gz"
➜ 20240822-grype-db-issues sha256sum vulnerability.db
4fdadd9a0d6d2c43ab18a5c3086145f15534206fed803aae2f18034bf5dca719 vulnerability.db
➜ 20240822-grype-db-issues jq '.checksum' metadata.json
"sha256:4fdadd9a0d6d2c43ab18a5c3086145f15534206fed803aae2f18034bf5dca719"
Scans are being performed successfully with this db.
Hi @philroche thanks for the report for reporting back that it's fixed! I'm glad things are working for you now.
Aside: I'm adding changelog-ignore
to this because no change was made in grype, only in the DB publishing infra.
Thanks for the quick turnaround
What happened: The grype db published on
2024-08-22 01:31:37 +0000 UTC
@ https://grype.anchore.io/databases/vulnerability-db_v5_2024-08-22T01:31:37Z_1724300383.tar.gz 's metadata.sjon checksum entry does not match the checksum of the vulnerability.db resulting in errorunable to update vulnerability database: bad db checksum (/tmp/grype-scratch1220908777/vulnerability.db): "sha256:a11915b8368897dd446ad5cbb855414870297841f8bccc3b466c5c5e9ba5539b" vs "sha256:9aba357712f1f68620ccd19349038e59f17a337189a075f9abea884591925f9b"
when trying to import.Using
grype
command directly to scan does not result in an issue but when using the https://pkg.go.dev/github.com/anchore/grype the issue is present.What you expected to happen: I expect the checksums to match as they have in previous db updates and imports and scan to succeed.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Example from the previous db published on
2024-08-21 01:31:31 +0000 UTC
Environment:
grype version
:cat /etc/os-release
or similar):