What is the severity of CVE-2021-22181?

CVE-2021-22181 is categorized as a denial of service vulnerability affecting all versions of GitLab since 11.8.

How do I fix CVE-2021-22181?

To mitigate CVE-2021-22181, it is recommended to upgrade GitLab to versions 13.10.6, 13.11.6, or 13.12.3 or later.

What versions of GitLab are affected by CVE-2021-22181?

CVE-2021-22181 affects all versions of GitLab CE/EE from 11.8.0 to 13.10.5, 13.11.0 to 13.11.5, and 13.12.0 to 13.12.2.

What kind of attack does CVE-2021-22181 enable?

CVE-2021-22181 allows an attacker to create recursive pipeline relationships, leading to resource exhaustion.

Is there a workaround for CVE-2021-22181?

Currently, there are no specific workarounds for CVE-2021-22181; upgrading to a fixed version is the recommended action.

Vulnerability/
CVE-2021-22181

high

7.7

CWE

400

11/6/2021

3/8/2024

CVE-2021-22181

First published: Fri Jun 11 2021(Updated: )

A denial of service vulnerability in GitLab CE/EE affecting all versions since 11.8 allows an attacker to create a recursive pipeline relationship and exhaust resources.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=11.8.0<13.10.5
GitLab	>=11.8.0<13.10.5
GitLab	>=13.11.0<13.11.5
GitLab	>=13.11.0<13.11.5
GitLab	>=13.12.0<13.12.2
GitLab	>=13.12.0<13.12.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-22181?
CVE-2021-22181 is categorized as a denial of service vulnerability affecting all versions of GitLab since 11.8.
How do I fix CVE-2021-22181?
To mitigate CVE-2021-22181, it is recommended to upgrade GitLab to versions 13.10.6, 13.11.6, or 13.12.3 or later.
What versions of GitLab are affected by CVE-2021-22181?
CVE-2021-22181 affects all versions of GitLab CE/EE from 11.8.0 to 13.10.5, 13.11.0 to 13.11.5, and 13.12.0 to 13.12.2.
What kind of attack does CVE-2021-22181 enable?
CVE-2021-22181 allows an attacker to create recursive pipeline relationships, leading to resource exhaustion.
Is there a workaround for CVE-2021-22181?
Currently, there are no specific workarounds for CVE-2021-22181; upgrading to a fixed version is the recommended action.

agent/references
agent/weakness
agent/author
agent/softwarecombine
agent/description
agent/type
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/11.8.0
version/gitlab/13.11.0
version/gitlab/13.12.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2021-22181?
CVE-2021-22181 is categorized as a denial of service vulnerability affecting all versions of GitLab since 11.8.
How do I fix CVE-2021-22181?
To mitigate CVE-2021-22181, it is recommended to upgrade GitLab to versions 13.10.6, 13.11.6, or 13.12.3 or later.
What versions of GitLab are affected by CVE-2021-22181?
CVE-2021-22181 affects all versions of GitLab CE/EE from 11.8.0 to 13.10.5, 13.11.0 to 13.11.5, and 13.12.0 to 13.12.2.
What kind of attack does CVE-2021-22181 enable?
CVE-2021-22181 allows an attacker to create recursive pipeline relationships, leading to resource exhaustion.
Is there a workaround for CVE-2021-22181?
Currently, there are no specific workarounds for CVE-2021-22181; upgrading to a fixed version is the recommended action.