CVE-2020-13302 [Low] | Security Vulnerability in Gitlab

A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. Under certain conditions GitLab was not properly revoking user sessions and allowed a malicious user to access a user account with an old password.

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

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.22%

1.13%

+0.91%

2025-11-21

0.12%

0.22%

+0.10%

2025-11-18

—

0.12%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
3.8	3.1	LOW	`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/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: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:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	1.2	2.5	[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]
6.5	2.0	MEDIUM	`AV:N/AC:L/Au:S/C:P/I:P/A:P` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:S) A single authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	8.0	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

3.8

3.1

LOW

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/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: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:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

1.2

2.5

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

6.5

2.0

MEDIUM

AV:N/AC:L/Au:S/C:P/I:P/A:P Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:S): A single authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

8.0

6.4

[email protected]

OS Trackers for CVE-2020-13302

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2020-13302 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-2020-13302
`ubuntu`	medium	CVE-2020-13302 medium priority: Ubuntu including 1 source packages (gitlab), 13 status rows across 13 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, trusty, upstream, xenial): DNE 11, ignored 1, released 1.	https://ubuntu.com/security/CVE-2020-13302

Affected software / configurations for CVE-2020-13302

Vendor	Product	Version	Raw CPE
gitlab	gitlab	< 13.1.10	cpe:2.3:a:gitlab:gitlab::::::::
gitlab	gitlab	>= 13.2.0, < 13.2.8	cpe:2.3:a:gitlab:gitlab::::::::
gitlab	gitlab	>= 13.3.0, < 13.3.4	cpe:2.3:a:gitlab:gitlab::::::::

References for CVE-2020-13302

URL	Tags
https://gitlab.com/gitlab-org/cves/-/blob/master/2020/CVE-2020-13302.json	Third Party Advisory
https://gitlab.com/gitlab-org/gitlab/-/issues/25195	Broken Link
https://hackerone.com/reports/437194	Permissions Required

URL

CVE-2020-13302

Exploit prediction scoring system (EPSS) score for CVE-2020-13302

Common vulnerability scoring system (CVSS) metrics for CVE-2020-13302

Weakness enumeration for CVE-2020-13302

OS Trackers for CVE-2020-13302

Affected software / configurations for CVE-2020-13302

References for CVE-2020-13302