Dec 8, 2017 - Brian Neel    

GitLab 10.2.4, 10.1.5, and 10.0.7 Released

Learn more about GitLab Release: 10.2.4, 10.1.5, and 10.0.7 for GitLab Community Edition (CE) and Enterprise Edition (EE)

Today we are releasing versions 10.2.4, 10.1.5, and 10.0.7 for GitLab Community Edition (CE) and Enterprise Edition (EE).

These versions contain several security fixes, including a fix for a difficult to exploit Cross-Site Scripting (XSS) vulnerability, a fix for an API bug that could leak the names of private projects, a fix for a private email disclosure vulnerability, and a fix for a bug that could allow users without access to a project to create issues in that project.

We recommend that all GitLab installations be upgraded to one of these versions.

Please read on for more details.

User without access to private Wiki can see it on the project page (#36679)

Matthias Burtscher reported that it was possible for a user to see a private Wiki on the project page without having the corresponding permission.

Versions affected: GitLab CE+EE 8.12.0–10.0.6, 10.1.0–10.1.4, 10.2.0–10.2.3

E-mail address disclosure through member search fields (#34910)

Hugo Geoffroy reported via HackerOne that it was possible to find out the full e-mail address of any user by brute-forcing the member search field.

Versions affected: GitLab CE+EE 8.6.0–10.0.6, 10.1.0–10.1.4, 10.2.0–10.2.3

Groups API leaks private projects (#39134)

An internal code review discovered that users were able to list private projects they had no access to by using the Groups API.

Versions affected: GitLab CE+EE 4.2.0–10.0.6, 10.1.0–10.1.4, 10.2.0–10.2.3

Cross-Site Scripting (XSS) possible by editing a comment (#40706)

Sylvain Heiniger reported via HackerOne that it was possible for arbitrary JavaScript code to be executed when editing a comment.

Versions affected: GitLab CE+EE 10.0.0–10.0.6, 10.1.0–10.1.4, 10.2.0–10.2.3

Issue API allows any user to create a new issue even when issues are restricted or disabled (#30663)

Mohammad Hasbini reported that any user could create a new issues in a project even when issues were disabled or restricted to team members in the project settings.

Versions affected: GitLab CE+EE 8.12.0–10.0.6, 10.1.0–10.1.4, 10.2.0–10.2.3

We recommend that all installations running a version mentioned above be upgraded as soon as possible. No workarounds are available for these vulnerabilities.

Upgrade barometer

These versions do not include any migrations and will not require 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