What is the severity of CVE-2022-2908?

CVE-2022-2908 is classified as a denial of service (DoS) vulnerability, which can lead to high CPU usage.

How do I fix CVE-2022-2908?

To mitigate CVE-2022-2908, update GitLab to version 15.1.5 or later, 15.2.3 or later, or 15.3.1 or later.

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

CVE-2022-2908 affects GitLab CE/EE versions starting from 10.7 up to 15.3 before 15.3.1.

What causes the CVE-2022-2908 vulnerability?

CVE-2022-2908 is caused by a specially crafted input in the commit message that can trigger excessive CPU usage.

Is CVE-2022-2908 exploitable remotely?

Yes, CVE-2022-2908 can be exploited remotely by sending a specially crafted commit message.

Vulnerability/
CVE-2022-2908

medium

4.3

CWE

1333

17/10/2022

3/8/2024

CVE-2022-2908

First published: Mon Oct 17 2022(Updated: )

A potential DoS vulnerability was discovered in Gitlab CE/EE versions starting from 10.7 before 15.1.5, all versions starting from 15.2 before 15.2.3, all versions starting from 15.3 before 15.3.1 allowed an attacker to trigger high CPU usage via a special crafted input added in the Commit message field.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=10.7.0<15.1.5
GitLab	>=10.7.0<15.1.5
GitLab	>=15.2<15.2.3
GitLab	>=15.2<15.2.3
GitLab	>=15.3<15.3.1
GitLab	>=15.3<15.3.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-2908?
CVE-2022-2908 is classified as a denial of service (DoS) vulnerability, which can lead to high CPU usage.
How do I fix CVE-2022-2908?
To mitigate CVE-2022-2908, update GitLab to version 15.1.5 or later, 15.2.3 or later, or 15.3.1 or later.
Which versions of GitLab are affected by CVE-2022-2908?
CVE-2022-2908 affects GitLab CE/EE versions starting from 10.7 up to 15.3 before 15.3.1.
What causes the CVE-2022-2908 vulnerability?
CVE-2022-2908 is caused by a specially crafted input in the commit message that can trigger excessive CPU usage.
Is CVE-2022-2908 exploitable remotely?
Yes, CVE-2022-2908 can be exploited remotely by sending a specially crafted commit message.

agent/type
agent/references
agent/weakness
agent/author
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/10.7.0
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.

Frequently Asked Questions

What is the severity of CVE-2022-2908?
CVE-2022-2908 is classified as a denial of service (DoS) vulnerability, which can lead to high CPU usage.
How do I fix CVE-2022-2908?
To mitigate CVE-2022-2908, update GitLab to version 15.1.5 or later, 15.2.3 or later, or 15.3.1 or later.
Which versions of GitLab are affected by CVE-2022-2908?
CVE-2022-2908 affects GitLab CE/EE versions starting from 10.7 up to 15.3 before 15.3.1.
What causes the CVE-2022-2908 vulnerability?
CVE-2022-2908 is caused by a specially crafted input in the commit message that can trigger excessive CPU usage.
Is CVE-2022-2908 exploitable remotely?
Yes, CVE-2022-2908 can be exploited remotely by sending a specially crafted commit message.