CVE-2024-8754 [Medium] | Input Validation Bypass in Gitlab

An issue has been discovered in GitLab EE/CE affecting all versions from 16.9.7 prior to 17.1.7, 17.2 prior to 17.2.5, and 17.3 prior to 17.3.2. An improper input validation error allows attacker to squat on accounts via linking arbitrary unclaimed provider identities when JWT authentication is configured.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-21	0.07%	0.02%	-0.04%
2	2025-11-18	0.04%	0.07%	+0.02%
3	2025-03-30	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-21

0.07%

0.02%

-0.04%

2025-11-18

0.04%

0.07%

+0.02%

2025-03-30

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.4	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N` 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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	1.2	5.2	[email protected]
8.1	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N` 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:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	2.8	5.2	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.4

3.1

MEDIUM

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N 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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

1.2

5.2

[email protected]

8.1

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N 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:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

2.8

5.2

[email protected]

OS Trackers for CVE-2024-8754

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

Affected software / configurations for CVE-2024-8754

Vendor	Product	Version	Raw CPE
gitlab	gitlab	>= 16.9.7, < 17.1.7	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 16.9.7, < 17.1.7	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 17.2.0, < 17.2.5	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 17.2.0, < 17.2.5	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 17.3.0, < 17.3.2	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 17.3.0, < 17.3.2	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*

References for CVE-2024-8754

URL	Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/464062	Broken Link

URL

CVE-2024-8754 | External Control of Critical State Data in GitLab

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

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

Weakness enumeration for CVE-2024-8754

OS Trackers for CVE-2024-8754

Affected software / configurations for CVE-2024-8754

References for CVE-2024-8754