What is the severity of CVE-2020-13354?

CVE-2020-13354 is classified as a DOS vulnerability affecting GitLab CE/EE, which can lead to high CPU usage.

How do I fix CVE-2020-13354?

To resolve CVE-2020-13354, upgrade GitLab to version 13.3.9 or later.

Which versions are affected by CVE-2020-13354?

CVE-2020-13354 affects GitLab versions from 12.6 to 13.3.8.

What kind of attack does CVE-2020-13354 facilitate?

CVE-2020-13354 facilitates a Denial of Service attack due to excessive CPU usage when processing certain container registry name checks.

Is CVE-2020-13354 present in both GitLab CE and EE versions?

Yes, CVE-2020-13354 impacts both GitLab Community Edition (CE) and Enterprise Edition (EE).

Vulnerability/
CVE-2020-13354

medium

4.3

CWE

400

17/11/2020

4/8/2024

CVE-2020-13354

First published: Tue Nov 17 2020(Updated: )

A potential DOS vulnerability was discovered in GitLab CE/EE starting with version 12.6. The container registry name check could cause exponential number of backtracks for certain user supplied values resulting in high CPU usage. Affected versions are: >=12.6, <13.3.9.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.6.0<13.3.9
GitLab	>=12.6.0<13.3.9

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-13354?
CVE-2020-13354 is classified as a DOS vulnerability affecting GitLab CE/EE, which can lead to high CPU usage.
How do I fix CVE-2020-13354?
To resolve CVE-2020-13354, upgrade GitLab to version 13.3.9 or later.
Which versions are affected by CVE-2020-13354?
CVE-2020-13354 affects GitLab versions from 12.6 to 13.3.8.
What kind of attack does CVE-2020-13354 facilitate?
CVE-2020-13354 facilitates a Denial of Service attack due to excessive CPU usage when processing certain container registry name checks.
Is CVE-2020-13354 present in both GitLab CE and EE versions?
Yes, CVE-2020-13354 impacts both GitLab Community Edition (CE) and Enterprise Edition (EE).

agent/references
agent/weakness
agent/author
agent/softwarecombine
agent/type
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/12.6.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-13354?
CVE-2020-13354 is classified as a DOS vulnerability affecting GitLab CE/EE, which can lead to high CPU usage.
How do I fix CVE-2020-13354?
To resolve CVE-2020-13354, upgrade GitLab to version 13.3.9 or later.
Which versions are affected by CVE-2020-13354?
CVE-2020-13354 affects GitLab versions from 12.6 to 13.3.8.
What kind of attack does CVE-2020-13354 facilitate?
CVE-2020-13354 facilitates a Denial of Service attack due to excessive CPU usage when processing certain container registry name checks.
Is CVE-2020-13354 present in both GitLab CE and EE versions?
Yes, CVE-2020-13354 impacts both GitLab Community Edition (CE) and Enterprise Edition (EE).