What is the severity of CVE-2022-3613?

The severity of CVE-2022-3613 is critical due to its potential to cause Denial of Service through high resource consumption.

How do I fix CVE-2022-3613?

To fix CVE-2022-3613, upgrade GitLab to version 15.5.7 or later, or to version 15.6.4 or later, or to version 15.7.2 or later.

Which versions of GitLab are affected by CVE-2022-3613?

CVE-2022-3613 affects all GitLab CE/EE versions prior to 15.5.7, between 15.6.0 and 15.6.4, and between 15.7.0 and 15.7.2.

What types of attacks are related to CVE-2022-3613?

CVE-2022-3613 relates to Denial of Service attacks exploiting crafted Prometheus Server queries that lead to excessive resource utilization.

Is there a workaround for CVE-2022-3613?

There are no documented workarounds for CVE-2022-3613, so updating to a patched version is essential.

Vulnerability/
CVE-2022-3613

high

7.5

12/1/2023

3/8/2024

CVE-2022-3613

First published: Thu Jan 12 2023(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions before 15.5.7, all versions starting from 15.6 before 15.6.4, all versions starting from 15.7 before 15.7.2. A crafted Prometheus Server query can cause high resource consumption and may lead to Denial of Service.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<15.5.7
GitLab	<15.5.7
GitLab	>=15.6.0<15.6.4
GitLab	>=15.6.0<15.6.4
GitLab	>=15.7.0<15.7.2
GitLab	>=15.7.0<15.7.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-3613?
The severity of CVE-2022-3613 is critical due to its potential to cause Denial of Service through high resource consumption.
How do I fix CVE-2022-3613?
To fix CVE-2022-3613, upgrade GitLab to version 15.5.7 or later, or to version 15.6.4 or later, or to version 15.7.2 or later.
Which versions of GitLab are affected by CVE-2022-3613?
CVE-2022-3613 affects all GitLab CE/EE versions prior to 15.5.7, between 15.6.0 and 15.6.4, and between 15.7.0 and 15.7.2.
What types of attacks are related to CVE-2022-3613?
CVE-2022-3613 relates to Denial of Service attacks exploiting crafted Prometheus Server queries that lead to excessive resource utilization.
Is there a workaround for CVE-2022-3613?
There are no documented workarounds for CVE-2022-3613, so updating to a patched version is essential.

agent/type
agent/references
agent/author
agent/softwarecombine
agent/description
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/15.6.0
version/gitlab/15.7.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-3613?
The severity of CVE-2022-3613 is critical due to its potential to cause Denial of Service through high resource consumption.
How do I fix CVE-2022-3613?
To fix CVE-2022-3613, upgrade GitLab to version 15.5.7 or later, or to version 15.6.4 or later, or to version 15.7.2 or later.
Which versions of GitLab are affected by CVE-2022-3613?
CVE-2022-3613 affects all GitLab CE/EE versions prior to 15.5.7, between 15.6.0 and 15.6.4, and between 15.7.0 and 15.7.2.
What types of attacks are related to CVE-2022-3613?
CVE-2022-3613 relates to Denial of Service attacks exploiting crafted Prometheus Server queries that lead to excessive resource utilization.
Is there a workaround for CVE-2022-3613?
There are no documented workarounds for CVE-2022-3613, so updating to a patched version is essential.