First published: Wed Apr 17 2019(Updated: )
An issue was discovered in GitLab Community and Enterprise Edition 10.x (starting from 10.8) and 11.x before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. It has Incorrect Access Control, a different vulnerability than CVE-2019-9732.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=10.8.0<=10.8.7 | |
GitLab | >=10.8.0<=10.8.7 | |
GitLab | >=11.0.0<11.6.10 | |
GitLab | >=11.0.0<11.6.10 | |
GitLab | >=11.8.0<11.8.1 | |
GitLab | >=11.8.0<11.8.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-9756 has a medium severity rating due to its Incorrect Access Control vulnerabilities.
To fix CVE-2019-9756, update GitLab to version 11.6.10 or later for versions 11.x, and for version 10.x upgrade to 10.8.8 or later.
CVE-2019-9756 affects GitLab Community and Enterprise Editions from versions 10.8.0 to 10.8.7, 11.0.0 to 11.6.10, and 11.8.0 to 11.8.1.
The impact of CVE-2019-9756 allows unauthorized users to access some GitLab resources due to access control misconfigurations.
Yes, CVE-2019-9756 is a different vulnerability from CVE-2019-9732, both affecting GitLab but with distinct issues.