What is the severity of CVE-2020-13280?

CVE-2020-13280 has a medium severity due to memory exhaustion caused by excessive logging.

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.

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.

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.

Are there any workarounds for CVE-2020-13280?

There are no official workarounds for CVE-2020-13280; upgrading to a patched version is recommended.

Vulnerability/
CVE-2020-13280

medium

6.5

CWE

400

13/8/2020

4/8/2024

CVE-2020-13280

First published: Thu 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.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<13.0.12
GitLab	<13.0.12
GitLab	>=13.1.0<13.1.6
GitLab	>=13.1.0<13.1.6
GitLab	>=13.2.0<13.2.3
GitLab	>=13.2.0<13.2.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-13280?
CVE-2020-13280 has a medium severity due to memory exhaustion caused by excessive logging.
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.
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.
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.
Are there any workarounds for CVE-2020-13280?
There are no official workarounds for CVE-2020-13280; upgrading to a patched version is recommended.

agent/references
agent/type
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

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2020-13280?
CVE-2020-13280 has a medium severity due to memory exhaustion caused by excessive logging.
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.
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.
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.
Are there any workarounds for CVE-2020-13280?
There are no official workarounds for CVE-2020-13280; upgrading to a patched version is recommended.