CVE-2022-2455: Medium severity gitlab vulnerability

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

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

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

Q: What type of issue is CVE-2022-2455 classified as?

CVE-2022-2455 is classified as a business logic issue causing resource exhaustion.

Q: Can unauthenticated users exploit CVE-2022-2455?

No, CVE-2022-2455 can only be exploited by authenticated and authorized users.

Published 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.

Affected Software

6 affected components

GitLab GitLab>=10.0.0<15.1.6

GitLab GitLab>=15.2<15.2.4

GitLab GitLab>=15.3<15.3.2

Event History

Oct 17, 2022

CVE Published

via MITRE·12:00 AM

Data Sourced

via MITRE·12:00 AM

DescriptionSeverityWeakness

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?