CVE-2020-13280: Medium severity gitlab vulnerability
Published Aug 13, 2020
·Updated
For GitLab before 13.0.12, 13.1.6, 13.2.3 a memory exhaustion flaw exists due to excessive logging of an invite email error message.
Affected Software
6 affected components
GitLab GitLab<13.0.12
GitLab GitLab<13.0.12
GitLab GitLab>=13.1.0<13.1.6
GitLab GitLab>=13.1.0<13.1.6
GitLab GitLab>=13.2.0<13.2.3
GitLab GitLab>=13.2.0<13.2.3
Event History
Aug 13, 2020
CVE Published
via MITRE·12:49 PM
Data Sourced
via MITRE·12:49 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-13280?
CVE-2020-13280 has a medium severity due to memory exhaustion caused by excessive logging.
2
How do I fix CVE-2020-13280?
To fix CVE-2020-13280, update GitLab to version 13.0.12, 13.1.6, or 13.2.3 or later.
3
What types of GitLab installations are affected by CVE-2020-13280?
CVE-2020-13280 affects both community and enterprise editions of GitLab versions prior to 13.0.12, as well as between 13.1.0 to 13.1.6 and 13.2.0 to 13.2.3.
4
What is the impact of CVE-2020-13280 on GitLab services?
The impact of CVE-2020-13280 can lead to potential service interruptions due to memory exhaustion.
5
Are there any workarounds for CVE-2020-13280?
There are no official workarounds for CVE-2020-13280; upgrading to a patched version is recommended.