GitLab 8.2.3 Released

Dec 10, 2015

Today we are releasing version 8.2.3 for Community Edition (CE) and Enterprise Edition (EE).

It includes the following fixes:

Remote code execution prevention

We found a vulnerability in GitLab where arbitrary Ruby objects could be instantiated with arbitrary data, because of an unsafe YAML load. This is the same problem that was found in Rails almost three years ago and was heavily publicized at that time.

The vulnerability can be turned into remote code execution when an object can be instantiated that evaluates one of its data attributes as Ruby code. At the time when the issue was found in Rails, Rails contained a number of classes that could be abused in this way, making it a RCE vulnerability.

In the version of Rails used in GitLab, these classes no longer meet the criteria, and we have been unable to find any other classes that do, which is why we currently consider this low-risk. However, someone with enough perseverance could likely find another class that can be abused in this way, so we recommend everyone to upgrade 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 GitLab EE.

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

Install GitLab on your own server in 2 minutes

Browse all posts

For the latest and most detailed news follow @gitlab on Twitter. Future blog posts suggestions.