What is the severity of CVE-2021-39915?

CVE-2021-39915 has been rated as a medium severity vulnerability due to improper access control allowing unauthorized access to project access token names.

How do I fix CVE-2021-39915?

To fix CVE-2021-39915, upgrade your GitLab installation to version 14.3.6 or above, 14.4.4 or above, or 14.5.2 or above.

What versions of GitLab are affected by CVE-2021-39915?

CVE-2021-39915 affects GitLab CE/EE versions starting from 13.0 before 14.3.6, 14.4 before 14.4.4, and 14.5 before 14.5.2.

What are the potential impacts of CVE-2021-39915?

The potential impact of CVE-2021-39915 includes exposure of project access token names, which could facilitate further attacks.

Is CVE-2021-39915 being exploited in the wild?

There have been no confirmed reports of CVE-2021-39915 being actively exploited in the wild, but it is advisable to apply patches promptly.

Vulnerability/
CVE-2021-39915

medium

5.3

CWE

668

13/12/2021

4/8/2024

CVE-2021-39915

First published: Mon Dec 13 2021(Updated: )

Improper access control in the GraphQL API in GitLab CE/EE affecting all versions starting from 13.0 before 14.3.6, all versions starting from 14.4 before 14.4.4, all versions starting from 14.5 before 14.5.2, allows an attacker to see the names of project access tokens on arbitrary projects

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.0.0<14.3.6
GitLab	>=13.0.0<14.3.6
GitLab	>=14.4.0<14.4.4
GitLab	>=14.4.0<14.4.4
GitLab	>=14.5.0<14.5.2
GitLab	>=14.5.0<14.5.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-39915?
CVE-2021-39915 has been rated as a medium severity vulnerability due to improper access control allowing unauthorized access to project access token names.
How do I fix CVE-2021-39915?
To fix CVE-2021-39915, upgrade your GitLab installation to version 14.3.6 or above, 14.4.4 or above, or 14.5.2 or above.
What versions of GitLab are affected by CVE-2021-39915?
CVE-2021-39915 affects GitLab CE/EE versions starting from 13.0 before 14.3.6, 14.4 before 14.4.4, and 14.5 before 14.5.2.
What are the potential impacts of CVE-2021-39915?
The potential impact of CVE-2021-39915 includes exposure of project access token names, which could facilitate further attacks.
Is CVE-2021-39915 being exploited in the wild?
There have been no confirmed reports of CVE-2021-39915 being actively exploited in the wild, but it is advisable to apply patches promptly.

agent/type
agent/references
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/13.0.0
version/gitlab/14.4.0
version/gitlab/14.5.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2021-39915?
CVE-2021-39915 has been rated as a medium severity vulnerability due to improper access control allowing unauthorized access to project access token names.
How do I fix CVE-2021-39915?
To fix CVE-2021-39915, upgrade your GitLab installation to version 14.3.6 or above, 14.4.4 or above, or 14.5.2 or above.
What versions of GitLab are affected by CVE-2021-39915?
CVE-2021-39915 affects GitLab CE/EE versions starting from 13.0 before 14.3.6, 14.4 before 14.4.4, and 14.5 before 14.5.2.
What are the potential impacts of CVE-2021-39915?
The potential impact of CVE-2021-39915 includes exposure of project access token names, which could facilitate further attacks.
Is CVE-2021-39915 being exploited in the wild?
There have been no confirmed reports of CVE-2021-39915 being actively exploited in the wild, but it is advisable to apply patches promptly.