Multiple versions of GitLab expose sensitive user credentials when assigning a user to an issue or merge request. A fix was included in versions 8.15.8, 8.16.7, and 8.17.4, which were released on March 20th 2017 at 23:59 UTC.
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Link | Tags |
---|---|
https://gitlab.com/gitlab-org/gitlab-ce/commit/cdf396f456472ef8decd9598daa8dc0097cd30c5 | patch vendor advisory |
https://gitlab.com/gitlab-org/gitlab-ce/commit/a70346fc6530aa28a98e4aa4cf0f40e2c3bcef6b | patch vendor advisory |
http://www.securityfocus.com/bid/97157 | vdb entry third party advisory |
https://gitlab.com/gitlab-org/gitlab-ce/commit/43f5a2739dbf8f5c4c16a79f98e2630888f6b5d1 | patch vendor advisory |
https://gitlab.com/gitlab-org/gitlab-ce/issues/29661 | exploit vendor advisory |
https://about.gitlab.com/2017/03/20/gitlab-8-dot-17-dot-4-security-release/ | release notes vendor advisory |