CVE-2019-9224: Medium severity gitlab vulnerability
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 4 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:39 PM
Data Sourced
via MITRE·04:39 PM
Description
Data Sourced
via NVD·05:29 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2019-9224?
CVE-2019-9224 is classified as having a moderate severity due to incorrect access control issues.
2
How do I fix CVE-2019-9224?
To fix CVE-2019-9224, upgrade GitLab Community or Enterprise Edition to version 11.6.10 or higher, 11.7.6 or higher, or 11.8.1 or higher.
3
What software is impacted by CVE-2019-9224?
CVE-2019-9224 affects GitLab Community and Enterprise Editions prior to versions 11.6.10, 11.7.6, and 11.8.1.
4
What type of vulnerability is CVE-2019-9224?
CVE-2019-9224 is an access control vulnerability that allows unauthorized access to certain functionality.
5
When was CVE-2019-9224 reported?
CVE-2019-9224 was reported on March 4, 2019, when the security release was made available.