UI issue and console errors for manually created vulnerabilities
Summary
When creating a vulnerability manually a Vue component tries to access a non-existing property on an object, which throws an error. This results in a broken UI and console errors (see screenshots below).
Steps to reproduce
- Go to a project's "Security & Compliance" -> "Vulnerability Report"
- Click on the "+ Submit vulnerability" button
- Fill out details and submit
- After being redirected to the newly submitted vulnerability's details page open your devtools
- Check for errors (see screenshot below)
- Check for the broken UI (see screenshot below)
Example Project
Manually created vulnerability:
https://gitlab.com/gitlab-org/secure/tests/vuln-dismiss-test/-/security/vulnerabilities/54006061
What is the current bug behavior?
- Console errors from Vue component
- Partly broken UI
What is the expected correct behavior?
- No console errors
- The UI is working as expected
Relevant logs and/or screenshots
| description | screenshot |
|---|---|
| console errors |  |
| UI |  |
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
Edited by David Pisek