CVE-2024-9633 [Low] | Security Vulnerability in Gitlab

An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.3 before 17.4.2, all versions starting from 17.5 before 17.5.4, all versions starting from 17.6 before 17.6.2. This issue allows an attacker to create a group with a name matching an existing unique Pages domain, potentially leading to domain confusion attacks.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.02%	0.44%	+0.42%
2	2025-11-21	0.12%	0.02%	-0.10%
3	2025-11-18	—	0.12%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.02%

0.44%

+0.42%

2025-11-21

0.12%

0.02%

-0.10%

2025-11-18

—

0.12%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
3.1	3.1	LOW	`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L` 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: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:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	1.6	1.4	[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

3.1

LOW

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L 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: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:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

1.6

1.4

[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-9633

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2024-9633 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-9633
`ubuntu`	medium	CVE-2024-9633 medium priority: Ubuntu including 1 source packages (gitlab), 6 status rows across 6 suites (focal, jammy, noble, oracular, upstream, xenial): DNE 4, ignored 1, released 1.	https://ubuntu.com/security/CVE-2024-9633

Affected software / configurations for CVE-2024-9633

Vendor	Product	Version	Raw CPE
gitlab	gitlab	>= 16.3.0, < 17.4.2	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 16.3.0, < 17.4.2	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 17.5.0, < 17.5.4	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 17.5.0, < 17.5.4	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 17.6.0, < 17.6.2	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 17.6.0, < 17.6.2	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*

References for CVE-2024-9633

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

URL

CVE-2024-9633 | Incorrect Ownership Assignment in GitLab

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

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

Weakness enumeration for CVE-2024-9633

OS Trackers for CVE-2024-9633

Affected software / configurations for CVE-2024-9633

References for CVE-2024-9633