2020-04-22 19:07:51 +05:30
---
type: reference, howto
2020-06-23 00:09:42 +05:30
stage: Secure
2020-07-28 23:09:34 +05:30
group: Threat Insights
2020-06-23 00:09:42 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
2020-04-22 19:07:51 +05:30
---
2020-10-24 23:57:45 +05:30
# Vulnerability Pages
2020-04-22 19:07:51 +05:30
2020-06-23 00:09:42 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13561) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 13.0.
2020-04-22 19:07:51 +05:30
2020-11-24 15:15:51 +05:30
Each security vulnerability in a project's [Security Dashboard ](../security_dashboard/index.md#project-security-dashboard ) has an individual page which includes:
2020-04-22 19:07:51 +05:30
2020-11-24 15:15:51 +05:30
- Details of the vulnerability.
- The status of the vulnerability within the project.
- Available actions for the vulnerability.
2021-01-03 14:25:43 +05:30
- Issues related to the vulnerability.
2020-04-22 19:07:51 +05:30
2020-10-24 23:57:45 +05:30
On the vulnerability page, you can interact with the vulnerability in
2020-04-22 19:07:51 +05:30
several different ways:
- [Change the Vulnerability Status ](#changing-vulnerability-status ) - You can change the
status of a vulnerability to **Detected** , **Confirmed** , **Dismissed** , or **Resolved** .
- [Create issue ](#creating-an-issue-for-a-vulnerability ) - Create a new issue with the
2020-06-23 00:09:42 +05:30
title and description pre-populated with information from the vulnerability report.
2020-04-22 19:07:51 +05:30
By default, such issues are [confidential ](../../project/issues/confidential_issues.md ).
2021-01-03 14:25:43 +05:30
- [Link issues ](#link-issues-to-the-vulnerability ) - Link existing issues to vulnerability.
2020-11-24 15:15:51 +05:30
- [Solution ](#automatic-remediation-for-vulnerabilities ) - For some vulnerabilities,
2020-04-22 19:07:51 +05:30
a solution is provided for how to fix the vulnerability.
## Changing vulnerability status
You can switch the status of a vulnerability using the **Status** dropdown to one of
the following values:
2020-07-28 23:09:34 +05:30
| Status | Description |
2020-04-22 19:07:51 +05:30
|-----------|-------------------------------------------------------------------|
| Detected | The default state for a newly discovered vulnerability |
| Confirmed | A user has seen this vulnerability and confirmed it to be real |
| Dismissed | A user has seen this vulnerability and dismissed it |
| Resolved | The vulnerability has been fixed and is no longer in the codebase |
2021-01-03 14:25:43 +05:30
A timeline shows you when the vulnerability status has changed,
and allows you to comment on a change.
2020-04-22 19:07:51 +05:30
## Creating an issue for a vulnerability
You can create an issue for a vulnerability by selecting the **Create issue** button.
This creates a [confidential issue ](../../project/issues/confidential_issues.md ) in the
2020-06-23 00:09:42 +05:30
project the vulnerability came from, and pre-populates it with useful information from
2020-04-22 19:07:51 +05:30
the vulnerability report. After the issue is created, GitLab redirects you to the
issue page so you can edit, assign, or comment on the issue.
2021-01-03 14:25:43 +05:30
## Link issues to the vulnerability
You can link one or more existing 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.
2020-11-24 15:15:51 +05:30
## Automatic remediation for vulnerabilities
2020-04-22 19:07:51 +05:30
You can fix some vulnerabilities by applying the solution that GitLab automatically
2020-11-24 15:15:51 +05:30
generates for you. [Read more about the automatic remediation for vulnerabilities feature ](../index.md#solutions-for-vulnerabilities-auto-remediation ).
