CVE-2022-3411

Description

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.

Categories

6.5
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.47%
Third-Party Advisory gitlab.com
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/376247 broken link
https://hackerone.com/reports/1685995 permissions required
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3411.json third party advisory

Frequently Asked Questions

What is the severity of CVE-2022-3411?
CVE-2022-3411 has been scored as a medium severity vulnerability.
How to fix CVE-2022-3411?
To fix CVE-2022-3411, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-3411 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-3411 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-3411?
CVE-2022-3411 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.