The 2.4 series release notes contain important changes in this release series.
- Migrating wikis to the new repository layout could fail if the original migration was interrupted before completion.
- Custom certificate authority (CA) certificates were not maintained across upgrades with SSL disabled.
- Protected branches could be updated when making a Git force push against multiple identical branches.
- Automatic Update Checking and downloading now checks for feature releases.
- MEDIUM Resolved a cross-site scripting (XSS) vulnerability.
- LOW The secure flag was not set for the
_gh_render cookie, potentially allowing the render cookie to be sent in plaintext HTTP requests. However, Enterprise sets the
Strict-Transport-Security header for modern browsers when SSL is enabled, which largely mitigates the issue.
- Packages have been updated to the latest security versions.
- We incorrectly redirect to the dashboard if you accessed GitHub Enterprise using an alias while in private mode. This might happen if you set a fully qualified domain name but the subdomain resolves correctly.
- 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.
- The management console settings interface doesn't clearly show if you have previously uploaded certificate files or a private key.
- Custom firewall rules aren't maintained during an upgrade.
- Enqueued background jobs are sometimes not purged when a repository is deleted.
- Trying to add a file to a repository with Subversion 1.9 clients incorrectly detects the file already exists and fails.
- On instances upgraded from 2.3 and earlier, restoring an archived protected branch will not restore all the settings correctly. This does not affect new instances.
- Automatic update checks fail to download the latest ESX package.
The GitHub Team