CVE-2019-9225: Infoleak
Published Apr 17, 2019
·Updated
An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. It has Incorrect Access Control (issue 5 of 5).
Affected Software
6 affected components
GitLab GitLab<11.6.10
GitLab GitLab<11.6.10
GitLab GitLab>=11.7.0<11.7.6
GitLab GitLab>=11.7.0<11.7.6
GitLab GitLab>=11.8.0<11.8.1
GitLab GitLab>=11.8.0<11.8.1
Event History
Apr 17, 2019
CVE Published
via MITRE·04:41 PM
Data Sourced
via MITRE·04:41 PM
Description
Data Sourced
via NVD·05:29 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2019-9225?
CVE-2019-9225 has been assigned a medium severity level due to incorrect access control issues.
2
How do I fix CVE-2019-9225?
To fix CVE-2019-9225, upgrade GitLab to version 11.6.10, 11.7.6, or 11.8.1 or later.
3
What versions of GitLab are affected by CVE-2019-9225?
CVE-2019-9225 affects GitLab Community and Enterprise Editions before versions 11.6.10, 11.7.6, and 11.8.1.
4
What kind of vulnerability is CVE-2019-9225?
CVE-2019-9225 is categorized as an Incorrect Access Control vulnerability.
5
Is CVE-2019-9225 present in both Community and Enterprise Editions of GitLab?
Yes, CVE-2019-9225 affects both the Community and Enterprise Editions of GitLab.