What is the severity of CVE-2021-39877?

CVE-2021-39877 has been rated as a high severity vulnerability due to its potential for causing uncontrolled resource consumption.

How do I fix CVE-2021-39877?

To mitigate CVE-2021-39877, upgrade your GitLab installation to version 14.1.7 or later, or 14.2.5 or later.

Which versions of GitLab are affected by CVE-2021-39877?

CVE-2021-39877 affects GitLab versions starting from 12.2.0 up to 14.1.7 and those in the 14.2.x stream before 14.2.5.

What types of attacks does CVE-2021-39877 enable?

CVE-2021-39877 allows attackers to exploit controlled resource consumption, potentially leading to service disruption.

Does CVE-2021-39877 affect both Community and Enterprise editions of GitLab?

Yes, CVE-2021-39877 affects both the Community and Enterprise editions of GitLab.

Vulnerability/
CVE-2021-39877

high

7.7

CWE

400

4/10/2021

4/8/2024

CVE-2021-39877

First published: Mon Oct 04 2021(Updated: )

A vulnerability was discovered in GitLab starting with version 12.2 that allows an attacker to cause uncontrolled resource consumption with a specially crafted file.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.2.0<14.1.7
GitLab	>=12.2.0<14.1.7
GitLab	>=14.2<14.2.5
GitLab	>=14.2<14.2.5
GitLab	>=14.3<14.3.1
GitLab	>=14.3<14.3.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-39877?
CVE-2021-39877 has been rated as a high severity vulnerability due to its potential for causing uncontrolled resource consumption.
How do I fix CVE-2021-39877?
To mitigate CVE-2021-39877, upgrade your GitLab installation to version 14.1.7 or later, or 14.2.5 or later.
Which versions of GitLab are affected by CVE-2021-39877?
CVE-2021-39877 affects GitLab versions starting from 12.2.0 up to 14.1.7 and those in the 14.2.x stream before 14.2.5.
What types of attacks does CVE-2021-39877 enable?
CVE-2021-39877 allows attackers to exploit controlled resource consumption, potentially leading to service disruption.
Does CVE-2021-39877 affect both Community and Enterprise editions of GitLab?
Yes, CVE-2021-39877 affects both the Community and Enterprise editions of GitLab.

agent/type
agent/references
agent/author
agent/weakness
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/12.2.0
version/gitlab/14.2
version/gitlab/14.3

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-2021-39877?
CVE-2021-39877 has been rated as a high severity vulnerability due to its potential for causing uncontrolled resource consumption.
How do I fix CVE-2021-39877?
To mitigate CVE-2021-39877, upgrade your GitLab installation to version 14.1.7 or later, or 14.2.5 or later.
Which versions of GitLab are affected by CVE-2021-39877?
CVE-2021-39877 affects GitLab versions starting from 12.2.0 up to 14.1.7 and those in the 14.2.x stream before 14.2.5.
What types of attacks does CVE-2021-39877 enable?
CVE-2021-39877 allows attackers to exploit controlled resource consumption, potentially leading to service disruption.
Does CVE-2021-39877 affect both Community and Enterprise editions of GitLab?
Yes, CVE-2021-39877 affects both the Community and Enterprise editions of GitLab.