CVE-2019-5472: High severity gitlab vulnerability
Published Jan 28, 2020
·Updated
An authorization issue was discovered in Gitlab versions < 12.1.2, < 12.0.4, and < 11.11.6 that prevented owners and maintainer to delete epic comments.
Affected Software
6 affected components
GitLab GitLab>=11.11.0<11.11.6
GitLab GitLab>=11.11.0<11.11.6
GitLab GitLab>=12.0.0<12.0.4
GitLab GitLab>=12.0.0<12.0.4
GitLab GitLab>=12.1.0<12.1.2
GitLab GitLab>=12.1.0<12.1.2
Remediation
Event History
Jan 28, 2020
CVE Published
via MITRE·02:52 AM
Data Sourced
via MITRE·02:52 AM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2019-5472?
CVE-2019-5472 is classified as a medium severity vulnerability due to its impact on GitLab's authorization processes.
2
How do I fix CVE-2019-5472?
To fix CVE-2019-5472, upgrade GitLab to versions 11.11.6, 12.0.4, or 12.1.2 or later.
3
What versions of GitLab are affected by CVE-2019-5472?
CVE-2019-5472 affects GitLab versions lower than 12.1.2, 12.0.4, and 11.11.6.
4
What is the impact of CVE-2019-5472 on GitLab users?
CVE-2019-5472 prevents owners and maintainers from deleting epic comments, potentially leading to unauthorized persistence of sensitive information.
5
Is there a workaround for CVE-2019-5472?
There is no documented workaround for CVE-2019-5472; the recommended action is to apply the appropriate patch by upgrading GitLab.