May 11, 2016 - GitLab  

GitLab 8.7.4 Released

Learn more about GitLab Release 8.7.4 for GitLab Community Edition (CE) and Enterprise Edition (EE)

Today we are releasing version 8.7.4 for GitLab Community Edition (CE) and Enterprise Edition (EE). This release includes two security fixes and as such we strongly recommend that all affected users upgrade their GitLab installations as soon as possible.

It includes the following fixes:

  • EE: Delete ProjectImportData record only if Project is not a mirror (!370)
  • EE: Fixed typo in GitLab Geo license check alert (!379)
  • CE/EE: Links for Redmine issue references are generated correctly again (!4048)
  • CE/EE: Fix setting trusted proxies (!3970)
  • CE/EE: Fix Bitbucket importer bug when throwing exceptions (!3941)
  • CE/EE: Use sign out path only if not empty (!3989)
  • CE/EE: Running rake gitlab:db:drop_tables now drops tables with cascade (!4020)
  • CE/EE: Running rake gitlab:db:drop_tables uses IF EXISTS as a precaution (!4100)

It also includes the following security fixes:

  • CE/EE: Use a case-insensitive comparison in sanitizing URI schemes (#17299)
  • EE: Fix LDAP access level spillover bug (#552)

XSS vulnerability via faulty URI scheme sanitization

The URI scheme of user-supplied links was not being properly sanitized. See the issue for more details.

Thanks to Anirudh Anand of 0daylabs for responsibly disclosing this issue to us.

GitLab Enterprise LDAP Group Sync

GitLab Enterprise Edition versions 8.7.0 through 8.7.3 contain an LDAP group sync bug that can lead to GitLab users being added to GitLab groups they do not belong to. We do not know if it is possible for a malicious GitLab user to reliably exploit this bug. Regardless of exploitability, when this bug strikes it makes unwanted changes to your project access controls.

Versions of GitLab EE prior to 8.7.0 are not affected by this bug. All versions of GitLab CE are not affected by this bug. If you are not using LDAP group synchronization in GitLab EE, you are not affected by this bug.

We recommend all users of GitLab EE 8.7.0 through 8.7.3 upgrade to 8.7.4 as soon as possible.

Upgrade barometer

This version does not include any new migrations, and should not require any downtime.

Please be aware that by default the Omnibus packages will stop, run migrations, and start again, no matter how “big” or “small” the upgrade is. This behavior can be changed by adding a /etc/gitlab/skip-auto-migrations file.


To update, check out our update page.

Enterprise Edition

Interested in GitLab Enterprise Edition? Check out the features exclusive to EE.

Access to GitLab Enterprise Edition is included with a subscription. No time to upgrade GitLab yourself? Subscribers receive upgrade and installation services.

We want to hear from you

Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum.

Share your feedback

Take GitLab for a spin

See what your team could do with The DevSecOps Platform.

Get free trial

Have a question? We're here to help.

Talk to an expert
Edit this page View source