CVE-2018-19572
N/A
Published: July 10, 2019 at 03:32 PM UTC
Updated: June 17, 2026 at 01:49 AM UTC
1 product affected across 1 vendorGitLab
Using N/A by N/A?
Get instant alerts when new vulnerabilities affect N/A - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.9%
Description
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.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
11.3.12 ≤ v < 11.4.811.4.9 ≤ v < 11.5.18.17.0 ≤ v < 11.3.118.3.0 ≤ v < 11.3.11
Affected range stops below 11.3.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 11.4.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 11.5.1, so it looks safe — our inference, not a vendor statement
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
References (2)
x_refsource_CONFIRMx_refsource_MISCRelease NotesVendor Advisory
Source: [email protected]
https://about.gitlab.com/2018/11/28/security-release-gitlab-11-dot-5-dot-1-released/x_refsource_MISCIssue TrackingVendor Advisory
Source: [email protected]
https://gitlab.com/gitlab-org/gitlab-pages/issues/98Quick Info
StatusMODIFIED
CWE
CWE-362
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card