What is the severity of CVE-2021-22167?

CVE-2021-22167 is considered to have a medium severity level.

How do I fix CVE-2021-22167?

To fix CVE-2021-22167, users should upgrade GitLab to version 13.5.6 or later, or to version 13.6.4 or later, or to version 13.7.2 or later.

What versions are affected by CVE-2021-22167?

CVE-2021-22167 affects all GitLab versions starting from 12.1.0 up to but not including 13.5.6, as well as specific ranges in 13.6.x and 13.7.x.

What type of attack is associated with CVE-2021-22167?

CVE-2021-22167 allows an attacker to gain temporary read access to private repositories due to incorrect headers on certain project pages.

Is CVE-2021-22167 applicable to both GitLab Community and Enterprise editions?

Yes, CVE-2021-22167 affects both GitLab Community and Enterprise editions.

Vulnerability/
CVE-2021-22167

high

7.5

15/1/2021

3/8/2024

CVE-2021-22167

First published: Fri Jan 15 2021(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 12.1. Incorrect headers in specific project page allows attacker to have a temporary read access to the private repository

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.1.0<13.5.6
GitLab	>=12.1.0<13.5.6
GitLab	>=13.6.0<13.6.4
GitLab	>=13.6.0<13.6.4
GitLab	>=13.7.0<13.7.2
GitLab	>=13.7.0<13.7.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-22167?
CVE-2021-22167 is considered to have a medium severity level.
How do I fix CVE-2021-22167?
To fix CVE-2021-22167, users should upgrade GitLab to version 13.5.6 or later, or to version 13.6.4 or later, or to version 13.7.2 or later.
What versions are affected by CVE-2021-22167?
CVE-2021-22167 affects all GitLab versions starting from 12.1.0 up to but not including 13.5.6, as well as specific ranges in 13.6.x and 13.7.x.
What type of attack is associated with CVE-2021-22167?
CVE-2021-22167 allows an attacker to gain temporary read access to private repositories due to incorrect headers on certain project pages.
Is CVE-2021-22167 applicable to both GitLab Community and Enterprise editions?
Yes, CVE-2021-22167 affects both GitLab Community and Enterprise editions.

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/12.1.0
version/gitlab/13.6.0
version/gitlab/13.7.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-22167?
CVE-2021-22167 is considered to have a medium severity level.
How do I fix CVE-2021-22167?
To fix CVE-2021-22167, users should upgrade GitLab to version 13.5.6 or later, or to version 13.6.4 or later, or to version 13.7.2 or later.
What versions are affected by CVE-2021-22167?
CVE-2021-22167 affects all GitLab versions starting from 12.1.0 up to but not including 13.5.6, as well as specific ranges in 13.6.x and 13.7.x.
What type of attack is associated with CVE-2021-22167?
CVE-2021-22167 allows an attacker to gain temporary read access to private repositories due to incorrect headers on certain project pages.
Is CVE-2021-22167 applicable to both GitLab Community and Enterprise editions?
Yes, CVE-2021-22167 affects both GitLab Community and Enterprise editions.