CVE-2022-1099: Medium severity GitLab GitLab vulnerability
Adding a very large number of tags to a runner in GitLab CE/EE affecting all versions prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 allows an attacker to impact the performance of GitLab
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 14.7.7 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 14.8.5 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 14.9.2
Event History
Frequently Asked Questions
What is the severity of CVE-2022-1099?
CVE-2022-1099 has been rated as a high severity vulnerability due to its impact on performance in GitLab.
Which versions of GitLab are affected by CVE-2022-1099?
CVE-2022-1099 affects all versions of GitLab prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2.
How do I fix CVE-2022-1099?
To fix CVE-2022-1099, upgrade your GitLab installation to version 14.7.7, 14.8.5, or 14.9.2 or later.
What type of vulnerability is CVE-2022-1099?
CVE-2022-1099 is a performance-related vulnerability allowing an attacker to degrade GitLab's performance.
What potential impact does CVE-2022-1099 have on GitLab?
CVE-2022-1099 can significantly impact the performance of GitLab, potentially leading to service disruptions.