What is the severity of CVE-2021-39943?

CVE-2021-39943 is classified as a medium severity vulnerability due to its potential impact on user authorization.

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

CVE-2021-39943 affects GitLab EE versions starting from 14.1 before 14.3.6, from 14.4 before 14.4.4, and from 14.5 before 14.5.2.

How do I fix CVE-2021-39943?

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

What impact does CVE-2021-39943 have on my GitLab instance?

CVE-2021-39943 can allow unauthorized users to update the status of checks via an API call, which could lead to manipulation of critical workflows.

Is there a workaround for CVE-2021-39943 while I update GitLab?

There is no official workaround for CVE-2021-39943; the recommended action is to apply the necessary updates as soon as possible.

Vulnerability/
CVE-2021-39943

medium

4.3

CWE

863

9/2/2022

4/8/2024

CVE-2021-39943

First published: Wed Feb 09 2022(Updated: )

An authorization logic error in the External Status Check API in GitLab EE affecting all versions starting from 14.1 before 14.3.6, all versions starting from 14.4 before 14.4.4, all versions starting from 14.5 before 14.5.2, allowed a user to update the status of the check via an API call

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=14.1.0<14.3.6
GitLab	>=14.4.0<14.4.4
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-39943?
CVE-2021-39943 is classified as a medium severity vulnerability due to its potential impact on user authorization.
What versions of GitLab are affected by CVE-2021-39943?
CVE-2021-39943 affects GitLab EE versions starting from 14.1 before 14.3.6, from 14.4 before 14.4.4, and from 14.5 before 14.5.2.
How do I fix CVE-2021-39943?
To fix CVE-2021-39943, upgrade GitLab EE to version 14.3.6 or later, 14.4.4 or later, or 14.5.2 or later.
What impact does CVE-2021-39943 have on my GitLab instance?
CVE-2021-39943 can allow unauthorized users to update the status of checks via an API call, which could lead to manipulation of critical workflows.
Is there a workaround for CVE-2021-39943 while I update GitLab?
There is no official workaround for CVE-2021-39943; the recommended action is to apply the necessary updates as soon as possible.

agent/type
agent/references
agent/weakness
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/14.1.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-39943?
CVE-2021-39943 is classified as a medium severity vulnerability due to its potential impact on user authorization.
What versions of GitLab are affected by CVE-2021-39943?
CVE-2021-39943 affects GitLab EE versions starting from 14.1 before 14.3.6, from 14.4 before 14.4.4, and from 14.5 before 14.5.2.
How do I fix CVE-2021-39943?
To fix CVE-2021-39943, upgrade GitLab EE to version 14.3.6 or later, 14.4.4 or later, or 14.5.2 or later.
What impact does CVE-2021-39943 have on my GitLab instance?
CVE-2021-39943 can allow unauthorized users to update the status of checks via an API call, which could lead to manipulation of critical workflows.
Is there a workaround for CVE-2021-39943 while I update GitLab?
There is no official workaround for CVE-2021-39943; the recommended action is to apply the necessary updates as soon as possible.