Skip to content

Manually created vulnerabilities link to wrong scanner

Summary

When creating a vulnerability manually through GraphQL, the vulnerabilityScanner does not show up for the vulnerability.

Steps to reproduce

  1. Create a new vulnerability through GraphQL or /-/security/vulnerabilities/new
  2. Call the GraphQL query 
    query {
  project(fullPath:"root/security-reports-evidence-test") {
    vulnerabilityScanners {
      nodes {
        name
        reportType
      }
    }
  }
}

Example Project

What is the current bug behavior?

The vulnerabilityScanners query is empty.

What is the expected correct behavior?

The vulnerabilityScanners query should show all of the vulnerability scanners, including the manual creation one.

Relevant logs and/or screenshots

ksnip_20220311-215014

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