What is the severity of CVE-2021-39900?

CVE-2021-39900 is classified as a medium severity vulnerability.

How do I fix CVE-2021-39900?

To fix CVE-2021-39900, upgrade GitLab to a version above 14.2.5 or 14.3.0.

What impact does CVE-2021-39900 have on GitLab?

CVE-2021-39900 allows information disclosure of full URLs for artifacts stored in object storage.

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

CVE-2021-39900 affects GitLab versions from 10.8.0 up to 14.1.7 and 14.2.0 up to 14.2.5.

Is CVE-2021-39900 a remote exploit?

CVE-2021-39900 does not require network access to exploit as it involves exposure through Rails logs.

Vulnerability/
CVE-2021-39900

medium

CWE

532

4/10/2021

4/8/2024

CVE-2021-39900

First published: Mon Oct 04 2021(Updated: )

Information disclosure from SendEntry in GitLab starting with 10.8 allowed exposure of full URL of artifacts stored in object-storage with a temporary availability via Rails logs.

Credit: cve@gitlab.com

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-39900?
CVE-2021-39900 is classified as a medium severity vulnerability.
How do I fix CVE-2021-39900?
To fix CVE-2021-39900, upgrade GitLab to a version above 14.2.5 or 14.3.0.
What impact does CVE-2021-39900 have on GitLab?
CVE-2021-39900 allows information disclosure of full URLs for artifacts stored in object storage.
Which versions of GitLab are affected by CVE-2021-39900?
CVE-2021-39900 affects GitLab versions from 10.8.0 up to 14.1.7 and 14.2.0 up to 14.2.5.
Is CVE-2021-39900 a remote exploit?
CVE-2021-39900 does not require network access to exploit as it involves exposure through Rails logs.

agent/references
agent/type
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/10.8.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-39900?
CVE-2021-39900 is classified as a medium severity vulnerability.
How do I fix CVE-2021-39900?
To fix CVE-2021-39900, upgrade GitLab to a version above 14.2.5 or 14.3.0.
What impact does CVE-2021-39900 have on GitLab?
CVE-2021-39900 allows information disclosure of full URLs for artifacts stored in object storage.
Which versions of GitLab are affected by CVE-2021-39900?
CVE-2021-39900 affects GitLab versions from 10.8.0 up to 14.1.7 and 14.2.0 up to 14.2.5.
Is CVE-2021-39900 a remote exploit?
CVE-2021-39900 does not require network access to exploit as it involves exposure through Rails logs.