Vulnerabilities · 2017 · Gitlab
CVE-2017-0882
Gitlab vulnerability
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.
Affected products
Gitlab. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Gitlab runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- about.gitlab.com/2017/03/20/gitlab-8-dot-17-dot-4-security-release/ · Vendor Advisory
- gitlab.com/gitlab-org/gitlab-ce/commit/43f5a2739dbf8f5c4c16a79f98e2630888f6b5d1 · Patch
- gitlab.com/gitlab-org/gitlab-ce/commit/a70346fc6530aa28a98e4aa4cf0f40e2c3bcef6b · Patch
- gitlab.com/gitlab-org/gitlab-ce/commit/cdf396f456472ef8decd9598daa8dc0097cd30c5 · Patch
- gitlab.com/gitlab-org/gitlab-ce/issues/29661 · Exploit
- www.securityfocus.com/bid/97157 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2017-0882
- cve.org/CVERecord?id=CVE-2017-0882
More vulnerabilities in Gitlab products
CVE-2026-8716CVE-2026-6713CVE-2026-5296CVE-2026-4868CVE-2026-2601CVE-2026-1751CVE-2026-1402CVE-2026-1102All 1,290
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.