CVE-2020-13299: High severity gitlab vulnerability
Published Sep 14, 2020
·Updated
A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. The revocation feature was not revoking all session tokens and one could re-use it to obtain a valid session.
Affected Software
6 affected components
GitLab GitLab>=13.1.0<13.1.10
GitLab GitLab>=13.1.0<13.1.10
GitLab GitLab>=13.2.0<13.2.8
GitLab GitLab>=13.2.0<13.2.8
GitLab GitLab>=13.3.0<13.3.4
GitLab GitLab>=13.3.0<13.3.4
Event History
Sep 14, 2020
CVE Published
via MITRE·06:36 PM
Data Sourced
via MITRE·06:36 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-13299?
CVE-2020-13299 is classified as a medium severity vulnerability due to its potential for session token reuse.
2
How do I fix CVE-2020-13299?
To fix CVE-2020-13299, upgrade GitLab to versions 13.1.10, 13.2.8, or 13.3.4 or later.
3
What systems are affected by CVE-2020-13299?
CVE-2020-13299 affects GitLab community and enterprise editions prior to versions 13.1.10, 13.2.8, and 13.3.4.
4
What type of vulnerability is CVE-2020-13299?
CVE-2020-13299 is a session management vulnerability that allows reuse of session tokens.
5
When was CVE-2020-13299 disclosed?
CVE-2020-13299 was disclosed in 2020 as part of the security updates for GitLab.