CVE-2022-1099
First published: Mon Apr 04 2022(Updated: )
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
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | <14.7.7 | |
| GitLab | <14.7.7 | |
| GitLab | >=14.8.0<14.8.5 | |
| GitLab | >=14.8.0<14.8.5 | |
| GitLab | >=14.9.0<14.9.2 | |
| GitLab | >=14.9.0<14.9.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
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.
- agent/references
- agent/type
- 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/14.8.0
- version/gitlab/14.9.0