First published: Mon Sep 09 2019(Updated: )
An issue was discovered in GitLab Community and Enterprise Edition 8.x, 9.x, 10.x, and 11.x before 11.5.8, 11.6.x before 11.6.6, and 11.7.x before 11.7.1. It has Incorrect Access Control. Users are able to comment on locked project issues.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=8.6.0<=8.17.8 | |
GitLab | >=8.6.0<=8.17.8 | |
GitLab | >=9.0.0<=9.3.7 | |
GitLab | >=9.0.0<=9.3.7 | |
GitLab | >=10.0.0<=10.8.7 | |
GitLab | >=10.0.0<=10.8.7 | |
GitLab | >=11.0.0<11.5.8 | |
GitLab | >=11.0.0<11.5.8 | |
GitLab | >=11.6.0<11.6.6 | |
GitLab | >=11.6.0<11.6.6 | |
GitLab | >=11.7.0<11.7.1 | |
GitLab | >=11.7.0<11.7.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-6995 has been classified with a severity rating that indicates potential risk due to improper access control.
To fix CVE-2019-6995, upgrading to GitLab versions 11.5.8, 11.6.6, or 11.7.1 and later is recommended.
CVE-2019-6995 affects GitLab Community and Enterprise Editions from versions 8.x to 11.5.7 and certain versions of 11.x.
CVE-2019-6995 is categorized as an Incorrect Access Control vulnerability impacting project issue comments.
Yes, CVE-2019-6995 allows users to comment on locked project issues due to improper access restrictions.