Vulnerability allowlisting no longer works with CS_SCHEMA_MODEL=15
Summary
As reported in gitlab-org/security-products/analyzers/container-scanning!2847 (comment 1321452364) the Vulnerability allowlisting feature for Container Scanning no longer works since the analyzer outputs a report that complies with v15 of the security report schema.
This is caused by the removal of the cve
property in v15 which is what the allowlisting feature seems to rely on. Though, the CVE information is still present in another property.
Steps to reproduce
Create .gitlab-ci.yml
include:
- template: Jobs/Container-Scanning.gitlab-ci.yml
container_scanning:
stage: container scanning
variables:
CS_IMAGE: ruby/3.1-slim
before_script:
- |
cat << EOF > vulnerability-allowlist.yml
generalallowlist:
# CRITICAL
CVE-2019-8457: N/A patched in bookworm mid-2023
CVE-2019-8457 will appear as non-allowed
Example Project
What is the current bug behavior?
The Vulnerability allowlisting feature for Container Scanning DOESN'T work for schema V15 compatible reports.
What is the expected correct behavior?
The Vulnerability allowlisting feature for Container Scanning works for schema V15 compatible reports.
Relevant logs and/or screenshots
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
Modify the implementation of the allowlisting feature to leverage the identifiers
array where the CVE information is normalized instead of the no longer provided cve
property.
Workaround: Set CS_SCHEMA_MODEL: 14
in you .gitlab-ci.yml
. NB: this won't be possible anymore when validation will reject v14 reports in %16.0