CVE-2017-0882Not scoredCWE-639

CVE-2017-0882: GitLab Community Edition and GitLab Enterprise Edition 8.7.0 through 8.15.7, 8.… vulnerability

Gitlab · GitLab Community Edition and GitLab Enterprise Edition 8.7.0 through 8.15.7, 8.…

Affected: GitLab Community Edition and GitLab Enterprise Edition 8.7.0 through 8.15.7, 8.… · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.1%probability of exploitation in the next 30 days

64th percentile

050100

Higher than 64% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

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…GitLab Community Edition and GitLab Enterprise Edition 8.7.…

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Insecure Direct Object Reference
Vendor: Gitlab
Published: March 2017
Band: Possible (1 to 10%), March 2017

CoverageNo articles yet

No CyberSIXT article names CVE-2017-0882 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.