CVE-2018-20500

Description

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.

Category

7.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.10%
Vendor Advisory gitlab.com Vendor Advisory gitlab.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://about.gitlab.com/blog/categories/releases/ release notes vendor advisory
https://about.gitlab.com/2018/12/31/security-release-gitlab-11-dot-6-dot-1-released/ release notes vendor advisory

Frequently Asked Questions

What is the severity of CVE-2018-20500?
CVE-2018-20500 has been scored as a high severity vulnerability.
How to fix CVE-2018-20500?
To fix CVE-2018-20500, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2018-20500 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2018-20500 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.