What is the severity of CVE-2021-39931?

CVE-2021-39931 is rated as a medium severity vulnerability.

How do I fix CVE-2021-39931?

To fix CVE-2021-39931, upgrade GitLab to version 14.3.6 or later, 14.4.4 or later, or 14.5.2 or later.

What versions are affected by CVE-2021-39931?

CVE-2021-39931 affects GitLab versions from 8.11 to 14.3.6, from 14.4 to 14.4.4, and from 14.5 to 14.5.2.

What does CVE-2021-39931 allow unauthorized users to do?

CVE-2021-39931 permits unauthorized project members to delete protected branches under certain conditions.

Is there a workaround for CVE-2021-39931 while waiting for a patch?

Currently, there are no published workarounds for CVE-2021-39931 until the system is updated to a secure version.

Vulnerability/
CVE-2021-39931

medium

4.3

13/12/2021

4/8/2024

CVE-2021-39931

First published: Mon Dec 13 2021(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions starting from 8.11 before 14.3.6, all versions starting from 14.4 before 14.4.4, all versions starting from 14.5 before 14.5.2. Under specific condition an unauthorised project member was allowed to delete a protected branches due to a business logic error.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=8.11.0<14.3.6
GitLab	>=8.11.0<14.3.6
GitLab	>=14.4.0<14.4.4
GitLab	>=14.4.0<14.4.4
GitLab	>=14.5.0<14.5.2
GitLab	>=14.5.0<14.5.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-39931?
CVE-2021-39931 is rated as a medium severity vulnerability.
How do I fix CVE-2021-39931?
To fix CVE-2021-39931, upgrade GitLab to version 14.3.6 or later, 14.4.4 or later, or 14.5.2 or later.
What versions are affected by CVE-2021-39931?
CVE-2021-39931 affects GitLab versions from 8.11 to 14.3.6, from 14.4 to 14.4.4, and from 14.5 to 14.5.2.
What does CVE-2021-39931 allow unauthorized users to do?
CVE-2021-39931 permits unauthorized project members to delete protected branches under certain conditions.
Is there a workaround for CVE-2021-39931 while waiting for a patch?
Currently, there are no published workarounds for CVE-2021-39931 until the system is updated to a secure version.

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/8.11.0
version/gitlab/14.4.0
version/gitlab/14.5.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-39931?
CVE-2021-39931 is rated as a medium severity vulnerability.
How do I fix CVE-2021-39931?
To fix CVE-2021-39931, upgrade GitLab to version 14.3.6 or later, 14.4.4 or later, or 14.5.2 or later.
What versions are affected by CVE-2021-39931?
CVE-2021-39931 affects GitLab versions from 8.11 to 14.3.6, from 14.4 to 14.4.4, and from 14.5 to 14.5.2.
What does CVE-2021-39931 allow unauthorized users to do?
CVE-2021-39931 permits unauthorized project members to delete protected branches under certain conditions.
Is there a workaround for CVE-2021-39931 while waiting for a patch?
Currently, there are no published workarounds for CVE-2021-39931 until the system is updated to a secure version.