CVE-2024-8973 [Medium] | Denial of Service in Gitlab

An issue has been discovered in GitLab CE/EE affecting all versions starting from 17.1 prior to 17.9.8, from 17.10 prior to 17.10.6, and from 17.11 prior to 17.11.2. It was possible to cause a DoS condition via GitHub import requests using a malicious crafted payload.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-03-05	0.05%	0.26%	+0.21%
2	2025-10-17	0.04%	0.05%	+0.01%
3	2025-10-04	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-03-05

0.05%

0.26%

+0.21%

2025-10-17

0.04%

0.05%

+0.01%

2025-10-04

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.5	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	3.6	[email protected]
7.5	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.5

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

3.6

[email protected]

7.5

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

3.6

[email protected]

OS Trackers for CVE-2024-8973

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2024-8973 not yet assigned priority: Debian including 1 source packages (gitlab), 1 status rows across 1 suites (sid): open 1.	https://security-tracker.debian.org/tracker/CVE-2024-8973
`ubuntu`	medium	CVE-2024-8973 medium priority: Ubuntu including 1 source packages (gitlab), 7 status rows across 7 suites (focal, jammy, noble, oracular, plucky, upstream, xenial): DNE 5, ignored 1, needs-triage 1.	https://ubuntu.com/security/CVE-2024-8973

Affected software / configurations for CVE-2024-8973

Vendor	Product	Version	Raw CPE
gitlab	gitlab	>= 17.1.0, < 17.9.8	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 17.1.0, < 17.9.8	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 17.10.0, < 17.10.6	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 17.10.0, < 17.10.6	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 17.11.0, < 17.11.2	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 17.11.0, < 17.11.2	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*

References for CVE-2024-8973

URL	Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/491041	Broken Link
https://hackerone.com/reports/2711684	Permissions Required

URL

CVE-2024-8973 | Allocation of Resources Without Limits or Throttling in GitLab

Exploit prediction scoring system (EPSS) score for CVE-2024-8973

Common vulnerability scoring system (CVSS) metrics for CVE-2024-8973

Weakness enumeration for CVE-2024-8973

OS Trackers for CVE-2024-8973

Affected software / configurations for CVE-2024-8973

References for CVE-2024-8973