What is the severity of CVE-2021-22252?

CVE-2021-22252 is classified as a medium severity vulnerability impacting GitLab.

How do I fix CVE-2021-22252?

To fix CVE-2021-22252, upgrade your GitLab instance to a version later than 13.12.9 or 14.0.7.

Who is affected by CVE-2021-22252?

CVE-2021-22252 affects all GitLab Community and Enterprise editions from version 13.7 to 14.1.2.

What does CVE-2021-22252 allow unauthorized access to?

CVE-2021-22252 allows Developers to access protected CI variables that should only be visible to Maintainers.

What versions of GitLab are vulnerable to CVE-2021-22252?

Versions of GitLab from 13.7.0 to 14.1.2 are vulnerable to CVE-2021-22252.

Vulnerability/
CVE-2021-22252

medium

6.5

23/8/2021

3/8/2024

CVE-2021-22252

First published: Mon Aug 23 2021(Updated: )

A confusion between tag and branch names in GitLab CE/EE affecting all versions since 13.7 allowed a Developer to access protected CI variables which should only be accessible to Maintainers

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.7.0<13.12.9
GitLab	>=13.7.0<13.12.9
GitLab	>=14.0.0<14.0.7
GitLab	>=14.0.0<14.0.7
GitLab	>=14.1.0<14.1.2
GitLab	>=14.1.0<14.1.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-22252?
CVE-2021-22252 is classified as a medium severity vulnerability impacting GitLab.
How do I fix CVE-2021-22252?
To fix CVE-2021-22252, upgrade your GitLab instance to a version later than 13.12.9 or 14.0.7.
Who is affected by CVE-2021-22252?
CVE-2021-22252 affects all GitLab Community and Enterprise editions from version 13.7 to 14.1.2.
What does CVE-2021-22252 allow unauthorized access to?
CVE-2021-22252 allows Developers to access protected CI variables that should only be visible to Maintainers.
What versions of GitLab are vulnerable to CVE-2021-22252?
Versions of GitLab from 13.7.0 to 14.1.2 are vulnerable to CVE-2021-22252.

agent/type
agent/references
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/13.7.0
version/gitlab/14.0.0
version/gitlab/14.1.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-22252?
CVE-2021-22252 is classified as a medium severity vulnerability impacting GitLab.
How do I fix CVE-2021-22252?
To fix CVE-2021-22252, upgrade your GitLab instance to a version later than 13.12.9 or 14.0.7.
Who is affected by CVE-2021-22252?
CVE-2021-22252 affects all GitLab Community and Enterprise editions from version 13.7 to 14.1.2.
What does CVE-2021-22252 allow unauthorized access to?
CVE-2021-22252 allows Developers to access protected CI variables that should only be visible to Maintainers.
What versions of GitLab are vulnerable to CVE-2021-22252?
Versions of GitLab from 13.7.0 to 14.1.2 are vulnerable to CVE-2021-22252.