Inconsistent vulnerability state between vuln details page and pipeline report
Summary
Status is sometimes inconsistent between the vulnerability details page and the pipeline Security tab entry for the same vulnerability.
Example: https://gitlab.com/gitlab-org/security-products/demos/imports/-/security/vulnerabilities/4394182
Note: The artifacts on the associated pipeline appear to have expired so the Security tab is now empty. Running a new pipeline will be necessary to repopulate findings.
Steps to reproduce
See video: #268285 (comment 451310093)
Example Project
What is the current bug behavior?
Different statuses are shown for the same vulnerability, depending on if you view its details page or information from the pipeline security tab.
What is the expected correct behavior?
A vulnerability's status should be the same everywhere.
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)