What is the severity of CVE-2023-0121?

CVE-2023-0121 has been classified as a denial of service vulnerability that can lead to high resource consumption.

Which versions are affected by CVE-2023-0121?

CVE-2023-0121 affects GitLab versions from 13.2.4 before 15.10.8, from 15.11 before 15.11.7, and from 16.0 before 16.0.2.

How do I fix CVE-2023-0121?

To fix CVE-2023-0121, upgrade your GitLab instance to the latest versions: 15.10.8, 15.11.7, or 16.0.2 and above.

What kind of attack can CVE-2023-0121 be used for?

CVE-2023-0121 can be exploited by attackers to cause denial of service through high resource consumption.

Is there a workaround for CVE-2023-0121?

Currently, the best approach for CVE-2023-0121 is to apply the necessary updates as there are no effective workarounds.

Vulnerability/
CVE-2023-0121

high

7.5

CWE

400 770

7/6/2023

7/1/2025

CVE-2023-0121: Allocation of Resources Without Limits or Throttling in GitLab

First published: Wed Jun 07 2023(Updated: )

A denial of service issue was discovered in GitLab CE/EE affecting all versions starting from 13.2.4 before 15.10.8, all versions starting from 15.11 before 15.11.7, all versions starting from 16.0 before 16.0.2 which allows an attacker to cause high resource consumption using malicious test report artifacts.

Credit: cve@gitlab.com cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.2.4<15.10.8
GitLab	>=13.2.4<15.10.8
GitLab	>=15.11.0<15.11.7
GitLab	>=15.11.0<15.11.7
GitLab	>=16.0.0<16.0.2
GitLab	>=16.0.0<16.0.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2023-0121?
CVE-2023-0121 has been classified as a denial of service vulnerability that can lead to high resource consumption.
Which versions are affected by CVE-2023-0121?
CVE-2023-0121 affects GitLab versions from 13.2.4 before 15.10.8, from 15.11 before 15.11.7, and from 16.0 before 16.0.2.
How do I fix CVE-2023-0121?
To fix CVE-2023-0121, upgrade your GitLab instance to the latest versions: 15.10.8, 15.11.7, or 16.0.2 and above.
What kind of attack can CVE-2023-0121 be used for?
CVE-2023-0121 can be exploited by attackers to cause denial of service through high resource consumption.
Is there a workaround for CVE-2023-0121?
Currently, the best approach for CVE-2023-0121 is to apply the necessary updates as there are no effective workarounds.

agent/type
agent/references
agent/description
agent/severity
agent/event
agent/first-publish-date
agent/weakness
agent/title
agent/author
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
agent/softwarecombine
agent/tags
collector/nvd-index
vendor/gitlab
canonical/gitlab
version/gitlab/13.2.4
version/gitlab/15.11.0
version/gitlab/16.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-2023-0121?
CVE-2023-0121 has been classified as a denial of service vulnerability that can lead to high resource consumption.
Which versions are affected by CVE-2023-0121?
CVE-2023-0121 affects GitLab versions from 13.2.4 before 15.10.8, from 15.11 before 15.11.7, and from 16.0 before 16.0.2.
How do I fix CVE-2023-0121?
To fix CVE-2023-0121, upgrade your GitLab instance to the latest versions: 15.10.8, 15.11.7, or 16.0.2 and above.
What kind of attack can CVE-2023-0121 be used for?
CVE-2023-0121 can be exploited by attackers to cause denial of service through high resource consumption.
Is there a workaround for CVE-2023-0121?
Currently, the best approach for CVE-2023-0121 is to apply the necessary updates as there are no effective workarounds.