What is the severity of CVE-2021-39866?

CVE-2021-39866 has been rated as a medium severity vulnerability.

How do I fix CVE-2021-39866?

To resolve CVE-2021-39866, upgrade GitLab to version 14.1.7 or later, or 14.2.5 or later.

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

CVE-2021-39866 affects GitLab versions from 13.6.0 to 14.1.6 and from 14.2.0 to 14.2.5.

What is the impact of CVE-2021-39866?

CVE-2021-39866 allows unauthorized persistent access via project access tokens due to a business logic error.

Is there a workaround for CVE-2021-39866 before upgrading?

There are no known effective workarounds for CVE-2021-39866, so upgrading is strongly recommended.

Vulnerability/
CVE-2021-39866

medium

5.5

5/10/2021

4/8/2024

CVE-2021-39866

First published: Tue Oct 05 2021(Updated: )

A business logic error in the project deletion process in GitLab 13.6 and later allows persistent access via project access tokens.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.6.0<14.1.7
GitLab	>=13.6.0<14.1.7
GitLab	>=14.2.0<14.2.5
GitLab	>=14.2.0<14.2.5
GitLab	=4.3.0
GitLab	=4.3.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-39866?
CVE-2021-39866 has been rated as a medium severity vulnerability.
How do I fix CVE-2021-39866?
To resolve CVE-2021-39866, upgrade GitLab to version 14.1.7 or later, or 14.2.5 or later.
Which versions of GitLab are affected by CVE-2021-39866?
CVE-2021-39866 affects GitLab versions from 13.6.0 to 14.1.6 and from 14.2.0 to 14.2.5.
What is the impact of CVE-2021-39866?
CVE-2021-39866 allows unauthorized persistent access via project access tokens due to a business logic error.
Is there a workaround for CVE-2021-39866 before upgrading?
There are no known effective workarounds for CVE-2021-39866, so upgrading is strongly recommended.

agent/type
agent/references
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.6.0
version/gitlab/14.2.0
version/gitlab/4.3.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-2021-39866?
CVE-2021-39866 has been rated as a medium severity vulnerability.
How do I fix CVE-2021-39866?
To resolve CVE-2021-39866, upgrade GitLab to version 14.1.7 or later, or 14.2.5 or later.
Which versions of GitLab are affected by CVE-2021-39866?
CVE-2021-39866 affects GitLab versions from 13.6.0 to 14.1.6 and from 14.2.0 to 14.2.5.
What is the impact of CVE-2021-39866?
CVE-2021-39866 allows unauthorized persistent access via project access tokens due to a business logic error.
Is there a workaround for CVE-2021-39866 before upgrading?
There are no known effective workarounds for CVE-2021-39866, so upgrading is strongly recommended.