CVE-2024-1211 [Medium] | CSRF in Gitlab

An issue has been discovered in GitLab CE/EE affecting all versions starting from 10.6 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2 in which cross-site request forgery may have been possible on GitLab instances configured to use JWT as an OmniAuth provider.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-01-31	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-01-31

—

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.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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: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:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[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.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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: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:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

OS Trackers for CVE-2024-1211

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2024-1211 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-1211
`ubuntu`	medium	CVE-2024-1211 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-1211

Affected software / configurations for CVE-2024-1211

Vendor	Product	Version	Raw CPE
gitlab	gitlab	>= 10.6.0, < 16.9.7	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 10.6.0, < 16.9.7	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 16.10.0, < 16.10.5	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 16.10.0, < 16.10.5	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 16.11.0, < 16.11.2	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	>= 16.11.0, < 16.11.2	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*

References for CVE-2024-1211

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

URL

CVE-2024-1211 | Cross-Site Request Forgery (CSRF) in GitLab

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

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

Weakness enumeration for CVE-2024-1211

OS Trackers for CVE-2024-1211

Affected software / configurations for CVE-2024-1211

References for CVE-2024-1211