What is the severity of CVE-2021-22246?

CVE-2021-22246 is classified as a denial of service vulnerability affecting GitLab versions before 14.0.2, 13.12.6, and 13.11.6.

How do I fix CVE-2021-22246?

To fix CVE-2021-22246, you should upgrade to GitLab versions 14.0.2, 13.12.6, or 13.11.6 or later.

Which versions of GitLab are affected by CVE-2021-22246?

CVE-2021-22246 affects GitLab Community and Enterprise editions prior to versions 14.0.2, 13.12.6, and 13.11.6.

What impact does CVE-2021-22246 have on GitLab users?

The impact of CVE-2021-22246 can result in denial of service attacks that disrupt the availability of GitLab services.

Is there any workaround for CVE-2021-22246?

There are no known workarounds for CVE-2021-22246; the recommended action is to upgrade to a fixed version.

Vulnerability/
CVE-2021-22246

high

7.7

CWE

770

20/8/2021

3/8/2024

CVE-2021-22246

First published: Fri Aug 20 2021(Updated: )

A vulnerability was discovered in GitLab versions before 14.0.2, 13.12.6, 13.11.6. GitLab Webhook feature could be abused to perform denial of service attacks.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=2.0.0<13.11.6
GitLab	>=2.0.0<13.11.6
GitLab	>=13.12.0<13.12.6
GitLab	>=13.12.0<13.12.6
GitLab	>=14.0.0<14.0.2
GitLab	>=14.0.0<14.0.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-22246?
CVE-2021-22246 is classified as a denial of service vulnerability affecting GitLab versions before 14.0.2, 13.12.6, and 13.11.6.
How do I fix CVE-2021-22246?
To fix CVE-2021-22246, you should upgrade to GitLab versions 14.0.2, 13.12.6, or 13.11.6 or later.
Which versions of GitLab are affected by CVE-2021-22246?
CVE-2021-22246 affects GitLab Community and Enterprise editions prior to versions 14.0.2, 13.12.6, and 13.11.6.
What impact does CVE-2021-22246 have on GitLab users?
The impact of CVE-2021-22246 can result in denial of service attacks that disrupt the availability of GitLab services.
Is there any workaround for CVE-2021-22246?
There are no known workarounds for CVE-2021-22246; the recommended action is to upgrade to a fixed version.

agent/type
agent/references
agent/weakness
agent/author
agent/softwarecombine
agent/description
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/2.0.0
version/gitlab/13.12.0
version/gitlab/14.0.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-22246?
CVE-2021-22246 is classified as a denial of service vulnerability affecting GitLab versions before 14.0.2, 13.12.6, and 13.11.6.
How do I fix CVE-2021-22246?
To fix CVE-2021-22246, you should upgrade to GitLab versions 14.0.2, 13.12.6, or 13.11.6 or later.
Which versions of GitLab are affected by CVE-2021-22246?
CVE-2021-22246 affects GitLab Community and Enterprise editions prior to versions 14.0.2, 13.12.6, and 13.11.6.
What impact does CVE-2021-22246 have on GitLab users?
The impact of CVE-2021-22246 can result in denial of service attacks that disrupt the availability of GitLab services.
Is there any workaround for CVE-2021-22246?
There are no known workarounds for CVE-2021-22246; the recommended action is to upgrade to a fixed version.