CVE-2022-2455
First published: Mon Oct 17 2022(Updated: )
A business logic issue in the handling of large repositories in all versions of GitLab CE/EE from 10.0 before 15.1.6, all versions starting from 15.2 before 15.2.4, all versions starting from 15.3 before 15.3.2 allowed an authenticated and authorized user to exhaust server resources by importing a malicious project.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=10.0.0<15.1.6 | |
| GitLab | >=10.0.0<15.1.6 | |
| GitLab | >=15.2<15.2.4 | |
| GitLab | >=15.2<15.2.4 | |
| GitLab | >=15.3<15.3.2 | |
| GitLab | >=15.3<15.3.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-2455?
CVE-2022-2455 is considered a high severity vulnerability due to its potential to exhaust server resources.
How do I fix CVE-2022-2455?
To mitigate CVE-2022-2455, update your GitLab installation to version 15.1.6 or later, or 15.2.4 or later, or 15.3.2 or later.
Who is affected by CVE-2022-2455?
CVE-2022-2455 affects all versions of GitLab CE/EE from 10.0 before 15.1.6, and specific versions up to 15.3.2.
What type of issue is CVE-2022-2455 classified as?
CVE-2022-2455 is classified as a business logic issue causing resource exhaustion.
Can unauthenticated users exploit CVE-2022-2455?
No, CVE-2022-2455 can only be exploited by authenticated and authorized users.
- agent/type
- agent/references
- 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/10.0.0
- version/gitlab/15.2
- version/gitlab/15.3