`grype:latest` scanner fails to load latest db, causing pipelines to fail
Summary
Attempting to scan containers with the image http://registry.gitlab.com/security-products/container-scanning/grype:latest
results in pipelines failing with the error
db could not be loaded: the vulnerability database was built 1 week ago (max allowed age is 5 days)
Steps to reproduce
Attempt to scan an image with CS_ANALYZER_IMAGE
set to registry.gitlab.com/security-products/container-scanning/grype:latest
and observe error in job output.
YAML used in testing:
include:
- template: Security/Container-Scanning.gitlab-ci.yml
container_scanning:
variables:
CS_ANALYZER_IMAGE: registry.gitlab.com/security-products/container-scanning/grype:latest
CS_IMAGE: "alpine:latest"
SECURE_LOG_LEVEL: debug
stage: test
Example Project
https://gitlab.com/brad/8802-grype
What is the current bug behavior?
Based on an internal Slack discussion, @zmartins determined that it looks like the latest
tag is pointing to 6.7.2
instead of 6.7.3
, causing the older image with the stale DB to loaded when the latest
tag is used.
What is the expected correct behavior?
The latest Grype scanner with the updated DB should be loaded when the latest
tag is used.
Relevant logs and/or screenshots
Link to output of failing job: https://gitlab.com/brad/8802-grype/-/jobs/7092536096#L531
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
Workaround
The workaround is to specify CS_ANALYZER_IMAGE: registry.gitlab.com/security-products/container-scanning/grype:6.7.3