CVE-2024-1495: Uncontrolled Resource Consumption in GitLab
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.10.7Fixed in 16.11.4Fixed in 17.0.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.10.7 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.11.4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 17.0.2
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
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.