What is the severity of CVE-2022-1121?

CVE-2022-1121 is considered a critical vulnerability due to the potential for unlimited resource consumption.

How do I fix CVE-2022-1121?

To fix CVE-2022-1121, upgrade to GitLab versions 14.7.7, 14.8.5, or 14.9.2 or later.

What systems are affected by CVE-2022-1121?

CVE-2022-1121 affects GitLab CE/EE versions prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2.

What type of attack does CVE-2022-1121 facilitate?

CVE-2022-1121 enables an attacker to launch Denial of Service (DoS) attacks through resource exhaustion.

Is CVE-2022-1121 present in all GitLab versions?

No, CVE-2022-1121 is only present in GitLab versions prior to the specified fixed versions.

Vulnerability/
CVE-2022-1121

medium

5.3

CWE

770

4/4/2022

2/8/2024

CVE-2022-1121

First published: Mon Apr 04 2022(Updated: )

A lack of appropriate timeouts in GitLab Pages included in GitLab CE/EE 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 cause unlimited resource consumption.

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

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-1121?
CVE-2022-1121 is considered a critical vulnerability due to the potential for unlimited resource consumption.
How do I fix CVE-2022-1121?
To fix CVE-2022-1121, upgrade to GitLab versions 14.7.7, 14.8.5, or 14.9.2 or later.
What systems are affected by CVE-2022-1121?
CVE-2022-1121 affects GitLab CE/EE versions prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2.
What type of attack does CVE-2022-1121 facilitate?
CVE-2022-1121 enables an attacker to launch Denial of Service (DoS) attacks through resource exhaustion.
Is CVE-2022-1121 present in all GitLab versions?
No, CVE-2022-1121 is only present in GitLab versions prior to the specified fixed versions.

agent/references
agent/weakness
agent/author
agent/softwarecombine
agent/description
agent/type
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

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-2022-1121?
CVE-2022-1121 is considered a critical vulnerability due to the potential for unlimited resource consumption.
How do I fix CVE-2022-1121?
To fix CVE-2022-1121, upgrade to GitLab versions 14.7.7, 14.8.5, or 14.9.2 or later.
What systems are affected by CVE-2022-1121?
CVE-2022-1121 affects GitLab CE/EE versions prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2.
What type of attack does CVE-2022-1121 facilitate?
CVE-2022-1121 enables an attacker to launch Denial of Service (DoS) attacks through resource exhaustion.
Is CVE-2022-1121 present in all GitLab versions?
No, CVE-2022-1121 is only present in GitLab versions prior to the specified fixed versions.