First published: Fri May 17 2019(Updated: )
An insecure permissions issue was discovered in GitLab Community and Enterprise Edition 9.4 and later but before 11.4.13, 11.5.x before 11.5.6, and 11.6.x before 11.6.1. The runner registration token in the CI/CD settings could not be reset. This was a security risk if one of the maintainers leaves the group and they know the token.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=9.4.0<11.4.13 | |
GitLab | >=9.4.0<11.4.13 | |
GitLab | >=11.5.0<11.5.6 | |
GitLab | >=11.5.0<11.5.6 | |
GitLab | >=11.6.0<11.6.1 | |
GitLab | >=11.6.0<11.6.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-20500 has been classified as a high severity vulnerability due to its potential to expose sensitive tokens.
To fix CVE-2018-20500, upgrade your GitLab instance to version 11.6.1 or later.
CVE-2018-20500 is associated with insecure permissions that affect the runner registration token in GitLab.
CVE-2018-20500 affects GitLab Community and Enterprise Editions from version 9.4 up to but not including 11.4.13, 11.5.x before 11.5.6, and 11.6.x before 11.6.1.
Users of GitLab who have maintainers that may leave the organization are at risk from CVE-2018-20500.