What is the severity of CVE-2021-39869?

CVE-2021-39869 has been classified as a medium severity vulnerability due to its potential to expose sensitive trigger tokens.

How do I fix CVE-2021-39869?

To fix CVE-2021-39869, upgrade to GitLab versions 14.2.6 or 14.1.8 or later.

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

CVE-2021-39869 affects all GitLab CE/EE versions from 8.9.0 to 14.1.7 and from 14.2.0 to 14.2.5.

What type of tokens are exposed by CVE-2021-39869?

CVE-2021-39869 exposes trigger tokens that are configured on the affected GitLab projects.

Is it safe to use versions prior to the patched update for CVE-2021-39869?

Using versions prior to the patched updates for CVE-2021-39869 is not safe due to the risk of exposing trigger tokens.

Vulnerability/
CVE-2021-39869

medium

6.5

5/10/2021

4/8/2024

CVE-2021-39869

First published: Tue Oct 05 2021(Updated: )

In all versions of GitLab CE/EE since version 8.9, project exports may expose trigger tokens configured on that project.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=8.9.0<14.1.7
GitLab	>=8.9.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-39869?
CVE-2021-39869 has been classified as a medium severity vulnerability due to its potential to expose sensitive trigger tokens.
How do I fix CVE-2021-39869?
To fix CVE-2021-39869, upgrade to GitLab versions 14.2.6 or 14.1.8 or later.
Which versions of GitLab are affected by CVE-2021-39869?
CVE-2021-39869 affects all GitLab CE/EE versions from 8.9.0 to 14.1.7 and from 14.2.0 to 14.2.5.
What type of tokens are exposed by CVE-2021-39869?
CVE-2021-39869 exposes trigger tokens that are configured on the affected GitLab projects.
Is it safe to use versions prior to the patched update for CVE-2021-39869?
Using versions prior to the patched updates for CVE-2021-39869 is not safe due to the risk of exposing trigger tokens.

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/8.9.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-39869?
CVE-2021-39869 has been classified as a medium severity vulnerability due to its potential to expose sensitive trigger tokens.
How do I fix CVE-2021-39869?
To fix CVE-2021-39869, upgrade to GitLab versions 14.2.6 or 14.1.8 or later.
Which versions of GitLab are affected by CVE-2021-39869?
CVE-2021-39869 affects all GitLab CE/EE versions from 8.9.0 to 14.1.7 and from 14.2.0 to 14.2.5.
What type of tokens are exposed by CVE-2021-39869?
CVE-2021-39869 exposes trigger tokens that are configured on the affected GitLab projects.
Is it safe to use versions prior to the patched update for CVE-2021-39869?
Using versions prior to the patched updates for CVE-2021-39869 is not safe due to the risk of exposing trigger tokens.