What is the severity of CVE-2024-1495?

CVE-2024-1495 has a severity rating that indicates it can lead to a denial of service.

How do I fix CVE-2024-1495?

To fix CVE-2024-1495, upgrade GitLab to version 16.10.7 or later, 16.11.4 or later, or 17.0.2 or later.

What versions are affected by CVE-2024-1495?

CVE-2024-1495 affects GitLab versions from 13.1 up to 16.10.6, from 16.11.0 up to 16.11.3, and from 17.0.0 up to 17.0.1.

Is CVE-2024-1495 a zero-day vulnerability?

CVE-2024-1495 is not classified as a zero-day vulnerability since it has been publicly disclosed and a fix is available.

Can CVE-2024-1495 be exploited remotely?

Yes, CVE-2024-1495 can be exploited remotely by an attacker using a maliciously crafted file.

Vulnerability/
CVE-2024-1495

medium

6.5

CWE

1333

12/6/2024

30/8/2024

CVE-2024-1495: Uncontrolled Resource Consumption in GitLab

First published: Wed Jun 12 2024(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.1 prior to 16.10.7, starting from 16.11 prior to 16.11.4, and starting from 17.0 prior to 17.0.2. It was possible for an attacker to cause a denial of service using maliciously crafted file.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.1<16.10.7
GitLab	>=13.1<16.10.7
GitLab	>=16.11.0<16.11.4
GitLab	>=16.11.0<16.11.4
GitLab	>=17.0.0<17.0.2
GitLab	>=17.0.0<17.0.2

Remedy

Upgrade to versions 16.10.7, 16.11.4, 17.0.2 or above.

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2024-1495?
CVE-2024-1495 has a severity rating that indicates it can lead to a denial of service.
How do I fix CVE-2024-1495?
To fix CVE-2024-1495, upgrade GitLab to version 16.10.7 or later, 16.11.4 or later, or 17.0.2 or later.
What versions are affected by CVE-2024-1495?
CVE-2024-1495 affects GitLab versions from 13.1 up to 16.10.6, from 16.11.0 up to 16.11.3, and from 17.0.0 up to 17.0.1.
Is CVE-2024-1495 a zero-day vulnerability?
CVE-2024-1495 is not classified as a zero-day vulnerability since it has been publicly disclosed and a fix is available.
Can CVE-2024-1495 be exploited remotely?
Yes, CVE-2024-1495 can be exploited remotely by an attacker using a maliciously crafted file.

agent/title
agent/references
agent/remedy
agent/first-publish-date
agent/description
agent/type
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/13.1
version/gitlab/16.11.0
version/gitlab/17.0.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-1495?
CVE-2024-1495 has a severity rating that indicates it can lead to a denial of service.
How do I fix CVE-2024-1495?
To fix CVE-2024-1495, upgrade GitLab to version 16.10.7 or later, 16.11.4 or later, or 17.0.2 or later.
What versions are affected by CVE-2024-1495?
CVE-2024-1495 affects GitLab versions from 13.1 up to 16.10.6, from 16.11.0 up to 16.11.3, and from 17.0.0 up to 17.0.1.
Is CVE-2024-1495 a zero-day vulnerability?
CVE-2024-1495 is not classified as a zero-day vulnerability since it has been publicly disclosed and a fix is available.
Can CVE-2024-1495 be exploited remotely?
Yes, CVE-2024-1495 can be exploited remotely by an attacker using a maliciously crafted file.