What is the severity of CVE-2018-19572?

CVE-2018-19572 has a high severity due to the potential for unauthorized access to files in the GitLab Pages chroot environment.

How do I fix CVE-2018-19572?

To fix CVE-2018-19572, upgrade to versions 11.5.1, 11.4.8, or 11.3.11 of GitLab.

Which versions of GitLab are affected by CVE-2018-19572?

GitLab CE version 8.17 and later and EE version 8.3 and later are affected by CVE-2018-19572.

Is CVE-2018-19572 present in GitLab's enterprise edition?

Yes, CVE-2018-19572 impacts both the GitLab Community Edition and the Enterprise Edition.

Vulnerability/
CVE-2018-19572

medium

5.9

CWE

362

10/7/2019

5/8/2024

CVE-2018-19572: Race Condition

Q: What type of vulnerability is CVE-2018-19572?

CVE-2018-19572 is a symlink time-of-check-to-time-of-use race condition vulnerability.

First published: Wed Jul 10 2019(Updated: )

GitLab CE 8.17 and later and EE 8.3 and later have a symlink time-of-check-to-time-of-use race condition that would allow unauthorized access to files in the GitLab Pages chroot environment. This is fixed in versions 11.5.1, 11.4.8, and 11.3.11.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=8.3.0<11.3.11
GitLab	>=8.17.0<11.3.11
GitLab	>=11.3.12<11.4.8
GitLab	>=11.3.12<11.4.8
GitLab	>=11.4.9<11.5.1
GitLab	>=11.4.9<11.5.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-19572?
CVE-2018-19572 has a high severity due to the potential for unauthorized access to files in the GitLab Pages chroot environment.
How do I fix CVE-2018-19572?
To fix CVE-2018-19572, upgrade to versions 11.5.1, 11.4.8, or 11.3.11 of GitLab.
Which versions of GitLab are affected by CVE-2018-19572?
GitLab CE version 8.17 and later and EE version 8.3 and later are affected by CVE-2018-19572.
What type of vulnerability is CVE-2018-19572?
CVE-2018-19572 is a symlink time-of-check-to-time-of-use race condition vulnerability.
Is CVE-2018-19572 present in GitLab's enterprise edition?
Yes, CVE-2018-19572 impacts both the GitLab Community Edition and the Enterprise Edition.

agent/references
agent/type
agent/severity
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
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/8.3.0
version/gitlab/8.17.0
version/gitlab/11.3.12
version/gitlab/11.4.9

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-2018-19572?
CVE-2018-19572 has a high severity due to the potential for unauthorized access to files in the GitLab Pages chroot environment.
How do I fix CVE-2018-19572?
To fix CVE-2018-19572, upgrade to versions 11.5.1, 11.4.8, or 11.3.11 of GitLab.
Which versions of GitLab are affected by CVE-2018-19572?
GitLab CE version 8.17 and later and EE version 8.3 and later are affected by CVE-2018-19572.
What type of vulnerability is CVE-2018-19572?
CVE-2018-19572 is a symlink time-of-check-to-time-of-use race condition vulnerability.
Is CVE-2018-19572 present in GitLab's enterprise edition?
Yes, CVE-2018-19572 impacts both the GitLab Community Edition and the Enterprise Edition.