The 2.13 series release notes contain important changes in this release series.
Git client vulnerabilities
A number of critical Git security vulnerabilities were recently announced that affect all versions of the official Git client.
We strongly recommend that you ensure that all users update their Git clients, in addition to upgrading to this GitHub Enterprise release.
More details on these vulnerabilities can be found in the official announcement, and the associated CVEs, CVE-2018-11233 and CVE-2018-11235.
- CRITICAL There was a remote code execution vulnerability that leveraged CVE-2018-11235 during the Pages build process. The Git package has been updated to address the vulnerability in the Pages build process. This fix is also available in GitHub Enterprise 2.13.2 and 2.13.3.
- GitHub will block pushing malicious Git submodules that could be used to exploit Git clients vulnerable to CVE-2018-11235.
- User passwords could end up being logged in plain text in the audit log.
- Elasticsearch metrics in the management console metrics dashboards have been fixed.
- Importing a Subversion repository that was created with an older version of Subversion would fail in specific scenarios.
- The GitHub Services deprecation warning contained a broken link to the deprecation announcement blog post.
- Increased performance of pull request reviewer selection box.
- Performance of issues and pull requests has been improved by ensuring data is properly cached.
- Enable marking one search index as primary when there are multiple primary Elasticsearch indexes listed.
- Images uploaded to issues save with an absolute URL, so they can be broken if the hostname changes.
- On a freshly set up GitHub Enterprise without any users, an attacker could create the first admin user.
- Custom firewall rules aren't maintained during an upgrade.
- svn checkout may timeout while the repository data cache is being built. In most cases, subsequent svn checkout attempts will succeed.
- Git LFS tracked files uploaded through the web interface are incorrectly added directly to the repository.
GitHub Enterprise clustering can not be configured without https.
- Pull request review comments are missing from an import with
- Nameid-format matching on SAML response is too strict when value is "unspecified", which can cause an error with the "Another user already owns the account." message if the IdP changes
NameID. (updated 2018-06-25)
- HTTPS is now a requirement of GitHub Enterprise clustering. (updated 2018-08-13)
The GitHub Team