CVE-2020-13307
First published: Tue Sep 15 2020(Updated: )
A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. GitLab was not revoking current user sessions when 2 factor authentication was activated allowing a malicious user to maintain their access.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=13.1.0<13.1.10 | |
| GitLab | >=13.1.0<13.1.10 | |
| GitLab | >=13.2.0<13.2.8 | |
| GitLab | >=13.2.0<13.2.8 | |
| GitLab | >=13.3.0<13.3.4 | |
| GitLab | >=13.3.0<13.3.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-13307?
CVE-2020-13307 has been classified with a high severity due to the potential for malicious users to maintain unauthorized access.
How do I fix CVE-2020-13307?
To fix CVE-2020-13307, upgrade GitLab to version 13.1.10, 13.2.8, or 13.3.4 or later.
What systems are affected by CVE-2020-13307?
CVE-2020-13307 affects all affected GitLab Community and Enterprise editions prior to versions 13.1.10, 13.2.8, and 13.3.4.
What is the impact of CVE-2020-13307?
The impact of CVE-2020-13307 allows attackers to maintain access by not revoking user sessions when two-factor authentication is enabled.
Is there a workaround for CVE-2020-13307?
There are no documented workarounds for CVE-2020-13307; upgrading to a patched version is required.
- agent/type
- agent/references
- agent/remedy
- agent/weakness
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/13.1.0
- version/gitlab/13.2.0
- version/gitlab/13.3.0