What is the severity of CVE-2021-39871?

CVE-2021-39871 has a high severity rating due to its potential to allow unauthorized access through API calls.

How do I fix CVE-2021-39871?

To fix CVE-2021-39871, update GitLab to version 14.1.7 or later if you are on versions 13.0.0 to 14.1.6, or to version 14.2.5 or later if you are on versions 14.2.0 to 14.2.4.

What versions of GitLab are affected by CVE-2021-39871?

CVE-2021-39871 affects GitLab CE and EE versions from 13.0 to 14.1.6 and 14.2.0 to 14.2.4.

What kind of attack does CVE-2021-39871 facilitate?

CVE-2021-39871 facilitates an attack that bypasses the setting to disable Bitbucket Server import via crafted API calls.

Is it possible to exploit CVE-2021-39871 without authentication?

Yes, CVE-2021-39871 can be exploited by unauthenticated users if the API call is crafted correctly.

Vulnerability/
CVE-2021-39871

medium

4.3

4/10/2021

4/8/2024

CVE-2021-39871

First published: Mon Oct 04 2021(Updated: )

In all versions of GitLab CE/EE since version 13.0, an instance that has the setting to disable Bitbucket Server import enabled is bypassed by an attacker making a crafted API call.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.0.0<14.1.7
GitLab	>=13.0.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-39871?
CVE-2021-39871 has a high severity rating due to its potential to allow unauthorized access through API calls.
How do I fix CVE-2021-39871?
To fix CVE-2021-39871, update GitLab to version 14.1.7 or later if you are on versions 13.0.0 to 14.1.6, or to version 14.2.5 or later if you are on versions 14.2.0 to 14.2.4.
What versions of GitLab are affected by CVE-2021-39871?
CVE-2021-39871 affects GitLab CE and EE versions from 13.0 to 14.1.6 and 14.2.0 to 14.2.4.
What kind of attack does CVE-2021-39871 facilitate?
CVE-2021-39871 facilitates an attack that bypasses the setting to disable Bitbucket Server import via crafted API calls.
Is it possible to exploit CVE-2021-39871 without authentication?
Yes, CVE-2021-39871 can be exploited by unauthenticated users if the API call is crafted correctly.

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.0.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-39871?
CVE-2021-39871 has a high severity rating due to its potential to allow unauthorized access through API calls.
How do I fix CVE-2021-39871?
To fix CVE-2021-39871, update GitLab to version 14.1.7 or later if you are on versions 13.0.0 to 14.1.6, or to version 14.2.5 or later if you are on versions 14.2.0 to 14.2.4.
What versions of GitLab are affected by CVE-2021-39871?
CVE-2021-39871 affects GitLab CE and EE versions from 13.0 to 14.1.6 and 14.2.0 to 14.2.4.
What kind of attack does CVE-2021-39871 facilitate?
CVE-2021-39871 facilitates an attack that bypasses the setting to disable Bitbucket Server import via crafted API calls.
Is it possible to exploit CVE-2021-39871 without authentication?
Yes, CVE-2021-39871 can be exploited by unauthenticated users if the API call is crafted correctly.