First published: Wed Jul 10 2019(Updated: )
GitLab CE/EE, versions 10.1 up to 11.x before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1, are vulnerable to an insecure direct object reference issue that allows a user to make comments on a locked issue.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=10.1.0<11.3.11 | |
GitLab | >=10.1.0<11.3.11 | |
GitLab | >=11.4.0<11.4.8 | |
GitLab | >=11.4.0<11.4.8 | |
GitLab | >=11.5.0<11.5.1 | |
GitLab | >=11.5.0<11.5.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-19575 has a moderate severity level due to the ability for users to comment on locked issues, which could lead to unwanted information disclosure.
CVE-2018-19575 allows unauthorized users to bypass locking mechanisms on issues, enabling them to leave comments where they shouldn't be able to.
To mitigate CVE-2018-19575, upgrade GitLab to version 11.3.11 or later, or to versions 11.4.8 and 11.5.1 or later.
CVE-2018-19575 affects GitLab Community Edition and Enterprise Edition versions from 10.1 up to but not including 11.3.11, 11.4 up to 11.4.8, and 11.5 up to 11.5.1.
CVE-2018-19575 is a notable vulnerability as it exposes a flaw in user permissions, making it significant for organizations using GitLab.