What is the severity of CVE-2024-1493?

CVE-2024-1493 is classified as a denial-of-service vulnerability affecting GitLab.

How do I fix CVE-2024-1493?

To fix CVE-2024-1493, upgrade GitLab to versions 16.11.5 or 17.0.3 and higher.

Who is affected by CVE-2024-1493?

CVE-2024-1493 affects all GitLab CE/EE versions from 9.2 to 16.11.5 and specific 17.x versions.

What types of attacks are possible with CVE-2024-1493?

CVE-2024-1493 can lead to a regular expression denial-of-service (ReDoS) attack due to vulnerable link processing logic.

When was CVE-2024-1493 discovered?

CVE-2024-1493 was reported in 2024 as an issue impacting multiple versions of GitLab.

Vulnerability/
CVE-2024-1493

medium

6.5

CWE

1333

26/6/2024

30/8/2024

CVE-2024-1493: Uncontrolled Resource Consumption in GitLab

First published: Wed Jun 26 2024(Updated: )

An issue was discovered in GitLab CE/EE affecting all versions starting from 9.2 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, with the processing logic for generating link in dependency files can lead to a regular expression DoS attack on the server

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=9.2.0<16.11.5
GitLab	>=9.2.0<16.11.5
GitLab	>=17.0.0<17.0.3
GitLab	>=17.0.0<17.0.3
GitLab	=17.1.0
GitLab	=17.1.0

Remedy

Upgrade to versions 17.1.1, 17.0.3, 16.11.5 or above.

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2024-1493?
CVE-2024-1493 is classified as a denial-of-service vulnerability affecting GitLab.
How do I fix CVE-2024-1493?
To fix CVE-2024-1493, upgrade GitLab to versions 16.11.5 or 17.0.3 and higher.
Who is affected by CVE-2024-1493?
CVE-2024-1493 affects all GitLab CE/EE versions from 9.2 to 16.11.5 and specific 17.x versions.
What types of attacks are possible with CVE-2024-1493?
CVE-2024-1493 can lead to a regular expression denial-of-service (ReDoS) attack due to vulnerable link processing logic.
When was CVE-2024-1493 discovered?
CVE-2024-1493 was reported in 2024 as an issue impacting multiple versions of GitLab.

agent/references
agent/type
agent/remedy
agent/description
agent/first-publish-date
agent/title
agent/severity
agent/author
agent/event
agent/softwarecombine
agent/last-modified-date
collector/mitre-cve
source/MITRE
agent/weakness
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/9.2.0
version/gitlab/17.0.0
version/gitlab/17.1.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-2024-1493?
CVE-2024-1493 is classified as a denial-of-service vulnerability affecting GitLab.
How do I fix CVE-2024-1493?
To fix CVE-2024-1493, upgrade GitLab to versions 16.11.5 or 17.0.3 and higher.
Who is affected by CVE-2024-1493?
CVE-2024-1493 affects all GitLab CE/EE versions from 9.2 to 16.11.5 and specific 17.x versions.
What types of attacks are possible with CVE-2024-1493?
CVE-2024-1493 can lead to a regular expression denial-of-service (ReDoS) attack due to vulnerable link processing logic.
When was CVE-2024-1493 discovered?
CVE-2024-1493 was reported in 2024 as an issue impacting multiple versions of GitLab.