CVE-2017-0882 Information disclosure in 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
GitLab exposes sensitive user credentials when assigning users to issues or merge requests, allowing attackers to read private data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2017-0882?
CVE-2017-0882 is a medium-severity vulnerability in Gitlab Gitlab, published on 28 Mar 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2017-0882?
It affects 1 product.
Products include Gitlab Gitlab.
How do I fix CVE-2017-0882?
No fix has been published for CVE-2017-0882 yet. Limit exposure of the affected software until one is available.
Is CVE-2017-0882 being exploited?
There is no known exploitation of CVE-2017-0882 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as GHSA-qgwf-v74m-338m.