CVE-2016-4340 in the critical feed json
The impersonate feature in Gitlab 8.7.0, 8.6.0 through 8.6.7, 8.5.0 through 8.5.11, 8.4.0 through 8.4.9, 8.3.0 through 8.3.8, and 8.2.0 thr…
published 2017-01-23 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-5340
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 10.1%
- EPSS 10.1% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
The impersonate feature in Gitlab 8.7.0, 8.6.0 through 8.6.7, 8.5.0 through 8.5.11, 8.4.0 through 8.4.9, 8.3.0 through 8.3.8, and 8.2.0 through 8.2.4 allows remote authenticated users to "log in" as any other user via unspecified vectors.
Patch / fix
Timeline
- First public exploit (EDB-40236)
- Published
Exploit prediction
10.14% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-40236 GitLab - 'impersonate' Feature Privilege Escalation webapps, 2016-08-15
- packetstormsecurity.com http://packetstormsecurity.com/files/138368/GitLab-Impersonate-Privilege-Escalation.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
- Technology feeds
References
-
about.gitlab.com
/2016/05/02/cve-2016-4340-patches/
mitigation, patch, vendor-advisory
-
gitlab.com
/gitlab-org/gitlab-ce/issues/15548
issue-tracking, patch, vendor-advisory
-
exploit-db.com
/exploits/40236/
exploit, third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/138368/GitLab-Impersonate-Privilege-Escalation.html
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2016-4340
- NVD CVE-2016-4340
Fencer Vulns 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.