CVE-2017-0882 json
Multiple versions of GitLab expose sensitive user credentials when assigning a user to an issue or merge request.
published 2017-03-28 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-1236
- cvss
- 6.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Exploit prediction
1.06% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- gitlab.com https://gitlab.com/gitlab-org/gitlab-ce/issues/29661 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.3 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected products
- n/a GitLab Community Edition and GitLab Enterprise Edition 8.7.0 through 8.15.7, 8.16.0 through 8.16.7, 8.17.0 through 8.17.3
Classification
- Weakness
- Technology feeds
References
-
gitlab.com
/gitlab-org/gitlab-ce/commit/cdf396f456472ef8decd9598daa8dc0097cd30c5
patch, vendor-advisory
-
gitlab.com
/gitlab-org/gitlab-ce/commit/a70346fc6530aa28a98e4aa4cf0f40e2c3bcef6b
patch, vendor-advisory
-
gitlab.com
/gitlab-org/gitlab-ce/commit/43f5a2739dbf8f5c4c16a79f98e2630888f6b5d1
patch, vendor-advisory
-
gitlab.com
/gitlab-org/gitlab-ce/issues/29661
exploit, vendor-advisory
-
about.gitlab.com
/2017/03/20/gitlab-8-dot-17-dot-4-security-release/
release-notes, vendor-advisory
-
securityfocus.com
/bid/97157
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-0882
- NVD CVE-2017-0882
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.