CVE-2021-22167: High severity gitlab vulnerability

Q: What is the severity of CVE-2021-22167?

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

Q: 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.

Q: 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.

Q: 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.

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

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

Published 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

Affected Software

6 affected components

GitLab GitLab>=12.1.0<13.5.6

GitLab GitLab>=13.6.0<13.6.4

GitLab GitLab>=13.7.0<13.7.2

Event History

Jan 15, 2021

CVE Published

via MITRE·03:12 PM

Data Sourced

via MITRE·03:12 PM

DescriptionSeverityWeakness

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?