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.
References
Link | Resource |
---|---|
https://about.gitlab.com/2018/12/31/security-release-gitlab-11-dot-6-dot-1-released/ | Release Notes Vendor Advisory |
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 |
https://about.gitlab.com/blog/categories/releases/ | Release Notes Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 04:01
Type | Values Removed | Values Added |
---|---|---|
References | () https://about.gitlab.com/2018/12/31/security-release-gitlab-11-dot-6-dot-1-released/ - Release Notes, Vendor Advisory | |
References | () https://about.gitlab.com/blog/categories/releases/ - Release Notes, Vendor Advisory |
Information
Published : 2019-05-17 16:29
Updated : 2024-11-21 04:01
NVD link : CVE-2018-20500
Mitre link : CVE-2018-20500
CVE.ORG link : CVE-2018-20500
JSON object : View
Products Affected
gitlab
- gitlab
CWE
CWE-732
Incorrect Permission Assignment for Critical Resource