cve.bz

CVE-2017-0882 gitlab gitlab

6.3 mediumExploit referenceEPSS 1.1%Fix available

Medium (6.3) in gitlab gitlab. EPSS 1.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.0

6.3 medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS
1.1% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 65th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-0882 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-0882?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-0882?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-0882 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
gitlab:gitlab8.2.0
gitlab:gitlab8.2.1
gitlab:gitlab8.2.2
gitlab:gitlab8.2.3
gitlab:gitlab8.2.4
gitlab:gitlab8.2.5
gitlab:gitlab8.3.0
gitlab:gitlab8.3.8
gitlab:gitlab8.3.9
gitlab:gitlab8.4.0
gitlab:gitlab8.4.9
gitlab:gitlab8.4.10
gitlab:gitlab8.5.0
gitlab:gitlab8.5.11
gitlab:gitlab8.5.12
gitlab:gitlab8.6.0
gitlab:gitlab8.6.7
gitlab:gitlab8.6.8
gitlab:gitlab8.7.0
gitlab:gitlab8.7.1
gitlab:gitlab8.10.0
gitlab:gitlab8.10.12
gitlab:gitlab8.10.13
gitlab:gitlab8.11.0
gitlab:gitlab8.11.9
gitlab:gitlab8.11.10
gitlab:gitlab8.12.0
gitlab:gitlab8.12.7
gitlab:gitlab8.12.8
gitlab:gitlab8.13.0
gitlab:gitlab8.13.2
gitlab:gitlab8.13.3
gitlab:gitlab8.14.0
gitlab:gitlab8.14.1
gitlab:gitlab8.14.2
gitlab:gitlab8.14.3
gitlab:gitlab8.14.4
gitlab:gitlab8.14.5
gitlab:gitlab8.14.6
gitlab:gitlab8.15.0
gitlab:gitlab8.15.1
gitlab:gitlab8.15.2
gitlab:gitlab8.15.3
gitlab:gitlab8.15.4
gitlab:gitlab8.15.5
gitlab:gitlab8.15.6
gitlab:gitlab8.15.7
gitlab:gitlab8.16.0
gitlab:gitlab8.16.1
gitlab:gitlab8.16.2
gitlab:gitlab8.16.3
gitlab:gitlab8.16.4
gitlab:gitlab8.16.5
gitlab:gitlab8.16.6
gitlab:gitlab8.16.7
gitlab:gitlab8.17.0
gitlab:gitlab8.17.1
gitlab:gitlab8.17.2
gitlab:gitlab8.17.3

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON