CVE-2019-18452: Medium severity gitlab vulnerability
Published Nov 26, 2019
·Updated
An issue was discovered in GitLab Community and Enterprise Edition 11.3 through 12.4 when moving an issue to a public project from a private one. It has Insecure Permissions.
Affected Software
2 affected components
GitLab GitLab>=11.3.0<=12.4.0
GitLab GitLab>=11.3.0<=12.4.0
Event History
Nov 26, 2019
CVE Published
via MITRE·04:41 PM
Data Sourced
via MITRE·04:41 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2019-18452?
CVE-2019-18452 has been classified with a medium severity due to its impact on permissions when moving issues between projects.
2
How do I fix CVE-2019-18452?
The recommended fix for CVE-2019-18452 is to upgrade to GitLab version 12.4.1 or later.
3
Which versions of GitLab are affected by CVE-2019-18452?
CVE-2019-18452 affects GitLab Community and Enterprise Editions from versions 11.3.0 to 12.4.0.
4
What consequences can occur if CVE-2019-18452 is exploited?
If exploited, CVE-2019-18452 can allow unauthorized access to sensitive project issues potentially leading to data exposure.
5
Is there a workaround for CVE-2019-18452?
There are no official workarounds for CVE-2019-18452; upgrading to the fixed version is necessary.