CVE-2024-3684 [High] | Privilege Escalation in Enterprise Server

A server side request forgery vulnerability was identified in GitHub Enterprise Server that allowed an attacker with an editor role in the Management Console to gain admin access to the appliance when configuring the Artifacts & Logs and Migrations Storage. Exploitation of this vulnerability required access to the GitHub Enterprise Server instance and access to the Management Console with the editor role. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.12 and was fixed in versions 3.12.2, 3.11.8, 3.10.10, and 3.9.13. This vulnerability was reported via the GitHub Bug Bounty program.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.69%	1.09%	+0.41%
2	2026-03-04	0.16%	0.69%	+0.53%
3	2026-03-01	—	0.16%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.69%

1.09%

+0.41%

2026-03-04

0.16%

0.69%

+0.53%

2026-03-01

—

0.16%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.0	3.1	HIGH	`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. 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.	1.3	6.0	[email protected]
7.2	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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:H) They need powerful rights—admin, root, or similar—before this pays off. 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:H) Could take the service down hard or make it unusable for people who depend on it.	1.2	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.0

3.1

HIGH

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
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.

1.3

6.0

[email protected]

7.2

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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:H): They need powerful rights—admin, root, or similar—before this pays off.
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:H): Could take the service down hard or make it unusable for people who depend on it.

1.2

5.9

[email protected]

Affected software / configurations for CVE-2024-3684

Vendor	Product	Version	Raw CPE
github	enterprise_server	< 3.9.13	cpe:2.3:a:github:enterprise_server::::::::
github	enterprise_server	>= 3.10.0, < 3.10.10	cpe:2.3:a:github:enterprise_server::::::::
github	enterprise_server	>= 3.11.0, < 3.11.8	cpe:2.3:a:github:enterprise_server::::::::
github	enterprise_server	>= 3.12.0, < 3.12.2	cpe:2.3:a:github:enterprise_server::::::::

References for CVE-2024-3684

URL	Tags
https://docs.github.com/en/[email protected]/admin/release-notes#3.10.10	Release Notes
https://docs.github.com/en/[email protected]/admin/release-notes#3.11.8	Release Notes
https://docs.github.com/en/[email protected]/admin/release-notes#3.12.2	Release Notes
https://docs.github.com/en/[email protected]/admin/release-notes#3.9.13	Release Notes

URL

CVE-2024-3684 | Improper Privilege Management was identified in GitHub Enterprise Server that allowed privilege escalation in the Management Console

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

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

Weakness enumeration for CVE-2024-3684

Affected software / configurations for CVE-2024-3684

References for CVE-2024-3684