Introduced in GitLab 13.4, only for public projects on GitLab.com.
CVE identifiers track specific vulnerabilities within projects. Having a CVE assigned to a vulnerability in your project helps your users stay secure and informed. For example, dependency scanning tools can detect when vulnerable versions of your project are used as a dependency.
If the following conditions are met, a Request CVE ID button appears in your issue sidebar:
- The project is hosted in GitLab.com.
- The project is public.
- You are a maintainer of the project.
- The issue is confidential.
Clicking the Request CVE ID button in the issue sidebar takes you to the new issue page for GitLab’s CVE project.
Creating the confidential issue starts the CVE request process.
You are required to fill in the issue description, which includes:
- A description of the vulnerability
- The project’s vendor and name
- Impacted versions
- Fixed versions
- The vulnerability type (a CWE identifier)
- A CVSS v3 vector
GitLab triages your submitted CVE ID request and communicates with you throughout the CVE validation and assignment process.
Once a CVE identifier is assigned, you may use and reference it as you see fit.
Details of the vulnerability submitted in the CVE ID request are published according to your schedule. It’s common to request a CVE for an unpatched vulnerability, reference the assigned CVE identifier in release notes, and later publish the vulnerability’s details after the fix is released.
Separate communications notify you when different stages of the publication process are complete.