What is the severity of CVE-2022-3411?

CVE-2022-3411 has a medium severity rating due to its impact on CPU usage under specific attack conditions.

How do I fix CVE-2022-3411?

To fix CVE-2022-3411, upgrade GitLab to the latest version above 15.6.7, 15.7.6, or 15.8.1.

What versions are affected by CVE-2022-3411?

CVE-2022-3411 affects all GitLab CE/EE versions starting from 12.4 up to 15.6.7, 15.7 up to 15.7.6, and 15.8 up to 15.8.1.

What type of attack is associated with CVE-2022-3411?

CVE-2022-3411 allows an authenticated attacker to create a large Issue description that can exploit CPU resources by repeated requests.

Is authentication required to exploit CVE-2022-3411?

Yes, an attacker must be authenticated to exploit CVE-2022-3411 and create a large Issue description.

Vulnerability/
CVE-2022-3411

medium

6.5

CWE

1284

13/2/2023

3/8/2024

CVE-2022-3411

First published: Mon Feb 13 2023(Updated: )

A lack of length validation in GitLab CE/EE affecting all versions from 12.4 before 15.6.7, 15.7 before 15.7.6, and 15.8 before 15.8.1 allows an authenticated attacker to create a large Issue description via GraphQL which, when repeatedly requested, saturates CPU usage.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.4<15.6.7
GitLab	>=12.4<15.6.7
GitLab	>=15.7<15.7.6
GitLab	>=15.7<15.7.6
GitLab	>=15.8<15.8.1
GitLab	>=15.8<15.8.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-3411?
CVE-2022-3411 has a medium severity rating due to its impact on CPU usage under specific attack conditions.
How do I fix CVE-2022-3411?
To fix CVE-2022-3411, upgrade GitLab to the latest version above 15.6.7, 15.7.6, or 15.8.1.
What versions are affected by CVE-2022-3411?
CVE-2022-3411 affects all GitLab CE/EE versions starting from 12.4 up to 15.6.7, 15.7 up to 15.7.6, and 15.8 up to 15.8.1.
What type of attack is associated with CVE-2022-3411?
CVE-2022-3411 allows an authenticated attacker to create a large Issue description that can exploit CPU resources by repeated requests.
Is authentication required to exploit CVE-2022-3411?
Yes, an attacker must be authenticated to exploit CVE-2022-3411 and create a large Issue description.

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

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-3411?
CVE-2022-3411 has a medium severity rating due to its impact on CPU usage under specific attack conditions.
How do I fix CVE-2022-3411?
To fix CVE-2022-3411, upgrade GitLab to the latest version above 15.6.7, 15.7.6, or 15.8.1.
What versions are affected by CVE-2022-3411?
CVE-2022-3411 affects all GitLab CE/EE versions starting from 12.4 up to 15.6.7, 15.7 up to 15.7.6, and 15.8 up to 15.8.1.
What type of attack is associated with CVE-2022-3411?
CVE-2022-3411 allows an authenticated attacker to create a large Issue description that can exploit CPU resources by repeated requests.
Is authentication required to exploit CVE-2022-3411?
Yes, an attacker must be authenticated to exploit CVE-2022-3411 and create a large Issue description.