What is the severity of CVE-2022-2931?

CVE-2022-2931 has a high severity rating due to its potential to cause denial of service (DoS) by consuming high CPU resources.

How do I fix CVE-2022-2931?

To fix CVE-2022-2931, you should upgrade your GitLab instance to version 15.1.6 or above, or to a secure version above 15.2.4 or 15.3.2.

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

CVE-2022-2931 affects all versions of GitLab before 15.1.6, as well as versions starting from 15.2 up to 15.2.4 and from 15.3 up to 15.3.2.

What can trigger the vulnerability described in CVE-2022-2931?

CVE-2022-2931 can be triggered by adding malformed content to the issue description in GitLab.

Is there a workaround for CVE-2022-2931?

There is no official workaround for CVE-2022-2931, and users are advised to upgrade to a patched version as soon as possible.

Vulnerability/
CVE-2022-2931

high

7.5

CWE

400

17/10/2022

3/8/2024

CVE-2022-2931

First published: Mon Oct 17 2022(Updated: )

A potential DOS vulnerability was discovered in GitLab CE/EE affecting all versions before 15.1.6, all versions starting from 15.2 before 15.2.4, all versions starting from 15.3 before 15.3.2. Malformed content added to the issue description could have been used to trigger high CPU usage.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<15.1.6
GitLab	<15.1.6
GitLab	>=15.2<15.2.4
GitLab	>=15.2<15.2.4
GitLab	>=15.3<15.3.2
GitLab	>=15.3<15.3.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-2931?
CVE-2022-2931 has a high severity rating due to its potential to cause denial of service (DoS) by consuming high CPU resources.
How do I fix CVE-2022-2931?
To fix CVE-2022-2931, you should upgrade your GitLab instance to version 15.1.6 or above, or to a secure version above 15.2.4 or 15.3.2.
Which versions of GitLab are affected by CVE-2022-2931?
CVE-2022-2931 affects all versions of GitLab before 15.1.6, as well as versions starting from 15.2 up to 15.2.4 and from 15.3 up to 15.3.2.
What can trigger the vulnerability described in CVE-2022-2931?
CVE-2022-2931 can be triggered by adding malformed content to the issue description in GitLab.
Is there a workaround for CVE-2022-2931?
There is no official workaround for CVE-2022-2931, and users are advised to upgrade to a patched version as soon as possible.

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/15.2
version/gitlab/15.3

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.