The 2.15 series release notes contain important changes in this release series.

Arbitrary file content disclosure vulnerability in GitHub Enterprise Server

A CRITICAL issue was identified in Rails that allows an attacker to send a specially crafted request that could allow arbitrary files to be read and the file content to be disclosed.

The affected supported versions are:

• 2.13.0 - 2.13.21
• 2.14.0 - 2.14.15
• 2.15.0 - 2.15.8
• 2.16.0 - 2.16.3

All older, no longer supported versions are also affected.

We strongly urge upgrading your GitHub Enterprise Server appliance to the latest patch release in your series, GitHub Enterprise Server 2.13.22, 2.14.16, 2.15.9, 2.16.4, or greater immediately. If you have any questions, please contact GitHub support at https://enterprise.github.com/support.

Security Fixes

• CRITICAL: A specially crafted request could allow arbitrary files to be read and the file content to be disclosed. For more information see the associated Rails CVE: CVE-2019-5418.
• HIGH: High CPU usage could be triggered by a specially crafted request resulting in Denial of Service (DoS). For more information see the associated Rails CVE: CVE-2019-5419.
• Packages have been updated to the latest security versions.

Bug Fixes

• Appliance upgrades could time out when updating significantly large databases.
• In rare circumstances, a race condition could lead to repository data loss if an automated background maintenance job was triggered during a configuration update.
• A pull request with a status check that was created by a deleted GitHub App would fail to load and showed a 500 error.
• A race condition during git operations sometimes caused the default branch to be assigned incorrectly.

Known Issues

• 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.
• Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
• Some pull requests and issues are purged completely when restoring the repository right after deleting it. (updated 2019-03-19)
• Resque workers may not be cleaned up following a configuration run leading to a growing number of stale workers which in turn could lead to high memory consumption. (updated 2019-05-08)

Thanks!

The GitHub Team