Vulnerability Pages

Each security vulnerability in a project’s Vulnerability Report has an individual page which includes:

  • Details of the vulnerability.
  • The status of the vulnerability within the project.
  • Available actions for the vulnerability.
  • Any issues related to the vulnerability.

On the vulnerability’s page, you can:

Change vulnerability status

You can change the status of a vulnerability using the Status dropdown to one of the following values:

Status Description
Detected The default state for a newly discovered vulnerability
Confirmed A user has seen this vulnerability and confirmed it to be accurate
Dismissed A user has seen this vulnerability and dismissed it because it is not accurate or otherwise not to be resolved
Resolved The vulnerability has been fixed and is no longer valid

A timeline shows you when the vulnerability status has changed and allows you to comment on a change.

Create a GitLab issue for a vulnerability

To create a GitLab issue for a vulnerability:

  1. In GitLab, go to the vulnerability’s page.
  2. Select Create issue.

An issue is created in the project, prepopulated with information from the vulnerability report. The issue is then opened so you can take further action.

Create a Jira issue for a vulnerability

Version history
cautionThis feature might not be available to you. Check the version history note above for details.

Prerequisites:

To create a Jira issue for a vulnerability:

  1. Go to the vulnerability’s page.
  2. Select Create Jira issue.

An issue is created in the linked Jira project, with the Summary and Description fields pre-populated. The Jira issue is then opened in a new browser tab.

Enable or disable Jira integration for vulnerabilities

The option to create a Jira issue for a vulnerability is under development but ready for production use. It is deployed behind a feature flag that is enabled by default. GitLab administrators with access to the GitLab Rails console can opt to disable it.

To enable it:

Feature.enable(:jira_for_vulnerabilities)

To disable it:

Feature.disable(:jira_for_vulnerabilities)
noteIf Jira issue support is enabled, GitLab issues are disabled so this feature is not available.

You can link one or more existing GitLab issues to the vulnerability. This allows you to indicate that this vulnerability affects multiple issues. It also allows you to indicate that the resolution of one issue would resolve multiple vulnerabilities.

Linked issues are shown in the Vulnerability Report and the vulnerability’s page.

Automatically remediate the vulnerability

You can fix some vulnerabilities by applying the solution that GitLab automatically generates for you. Read more about the automatic remediation for vulnerabilities feature.