What is the severity of CVE-2021-39870?

CVE-2021-39870 is rated as a medium-severity vulnerability due to the potential for unauthorized access to repository imports.

How do I fix CVE-2021-39870?

To mitigate CVE-2021-39870, update GitLab to a patched version beyond 14.1.7, 14.2.5, or 14.3.1.

What environments are affected by CVE-2021-39870?

CVE-2021-39870 affects all versions of GitLab CE/EE from 11.11.0 up to 14.3.1.

Is CVE-2021-39870 being actively exploited?

At this time, there are no public reports of active exploitation specifically targeting CVE-2021-39870.

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

CVE-2021-39870 allows attackers to bypass the Repo by URL import restriction via crafted API calls.

Vulnerability/
CVE-2021-39870

medium

4.3

5/10/2021

4/8/2024

CVE-2021-39870

First published: Tue Oct 05 2021(Updated: )

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

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=11.11.0<14.1.7
GitLab	>=11.11.0<14.1.7
GitLab	>=14.2.0<14.2.5
GitLab	>=14.2.0<14.2.5
GitLab	>=14.3.0<14.3.1
GitLab	>=14.3.0<14.3.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-39870?
CVE-2021-39870 is rated as a medium-severity vulnerability due to the potential for unauthorized access to repository imports.
How do I fix CVE-2021-39870?
To mitigate CVE-2021-39870, update GitLab to a patched version beyond 14.1.7, 14.2.5, or 14.3.1.
What environments are affected by CVE-2021-39870?
CVE-2021-39870 affects all versions of GitLab CE/EE from 11.11.0 up to 14.3.1.
Is CVE-2021-39870 being actively exploited?
At this time, there are no public reports of active exploitation specifically targeting CVE-2021-39870.
What kind of attack does CVE-2021-39870 facilitate?
CVE-2021-39870 allows attackers to bypass the Repo by URL import restriction via crafted API calls.

agent/type
agent/references
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/11.11.0
version/gitlab/14.2.0
version/gitlab/14.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-39870?
CVE-2021-39870 is rated as a medium-severity vulnerability due to the potential for unauthorized access to repository imports.
How do I fix CVE-2021-39870?
To mitigate CVE-2021-39870, update GitLab to a patched version beyond 14.1.7, 14.2.5, or 14.3.1.
What environments are affected by CVE-2021-39870?
CVE-2021-39870 affects all versions of GitLab CE/EE from 11.11.0 up to 14.3.1.
Is CVE-2021-39870 being actively exploited?
At this time, there are no public reports of active exploitation specifically targeting CVE-2021-39870.
What kind of attack does CVE-2021-39870 facilitate?
CVE-2021-39870 allows attackers to bypass the Repo by URL import restriction via crafted API calls.