Enterprise Server 3.4 release notes
Enterprise Server 3.4.18
Download GitHub Enterprise Server 3.4.18March 23, 2023
š£ This is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.
3.4.18: Security fixes
HIGH: Addressed an improper authentication vulnerability that allowed an unauthorized actor to modify other users' secret gists by authenticating through an SSH certificate authority. This vulnerability was reported via theĀ GitHub Bug Bounty ProgramĀ and has been assignedĀ CVE-2023-23761. [Updated: 2023-04-07]
MEDIUM: Addressed an incorrect comparison vulnerability that allowed commit smuggling by displaying an incorrect diff. This vulnerability was reported via theĀ GitHub Bug Bounty ProgramĀ and has been assignedĀ CVE-2023-23762. [Updated: 2023-04-07]
3.4.18: Bug fixes
In the Management Console's monitor dashboard, the
Cached RequestsandServed Requestsgraphs, which are retrieved by thegit fetch catchingcommand, did not display metrics for the instance.After a site administrator exempted the @github-actions[bot] user from rate limiting by using the
ghe-config app.github.rate-limiting-exempt-users "github-actions[bot]"command, runningghe-config-checkcaused aValidation is-valid-characterset failedwarning to appear.GitHub Actions (
actions) and Microsoft SQL (mssql) did not appear in the list of processes within the instances monitor dashboard.On an instance in a high availability configuration, if an administrator tore down replication from a replica node using
ghe-repl-teardownimmediately after runningghe-repl-setup, but beforeghe-repl-start, an error indicated that the scriptcannot launch /usr/local/bin/ghe-single-config-apply - run is locked.ghe-repl-teardownnow displays an informational alert and continues the teardown.On an instance in a cluster configuration, when a site administrator set maintenance mode using
ghe-maintenance -s, aPermission deniederror appeared when the utility tried to access/data/user/common/cluster.conf.When a site administrator used
ghe-migratorto migrate data to GitHub Enterprise Server, in some cases, nested team relationships would not persist after teams were imported.GitHub Enterprise Server published distribution metrics that cannot be processed by collectd. The metrics included
pre_receive.lfsintegrity.dist.referenced_oids,pre_receive.lfsintegrity.dist.unknown_oids, andgit.hooks.runtime.
3.4.18: Changes
After an enterprise owner enables Dependabot updates, the instance creates the initial set of updates faster.
On an instance in a cluster configuration, when a site administrator sets maintenance mode on a single cluster node using
ghe-maintenance -s, the utility warns the administrator to useghe-cluster-maintenance -sto set maintenance mode on all of the clusters nodes. For more information, see "Enabling and scheduling maintenance mode."When a site administrator configures an outbound web proxy server for GitHub Enterprise Server, the instance now validates top-level domains (TLDs) excluded from the proxy configuration. By default, you can exclude public TLDs that the IANA specifies. Site administrators can specify a list of unregistered TLDs to exclude using
ghe-config. The.prefix is required for any public TLDs. For example,.example.comis valid, butexample.comis invalid. For more information, see "Configuring an outbound web proxy server."The default path for output from
ghe-saml-mapping-csv -dis/data/user/tmpinstead of/tmp. For more information, see "Command-line utilities."
3.4.18: Known issues
On a freshly set up GitHub Enterprise Server instance without any users, an attacker could create the first admin user.
Custom firewall rules are removed during the upgrade process.
Git LFS tracked files uploaded through the web interface are incorrectly added directly to the repository.
The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
Hotpatch upgrades to GitHub Enterprise Server 3.4.9 may fail. Upgrades with the full
.pkgare unaffected. If the upgrade fails for your instance, workaround this issue by connecting to the administrative shell (ssh) and running the following non-interactive command:echo "grub-pc grub-pc/install_devices_empty boolean true" | sudo debconf-set-selectionsIf you're unable to upgrade, or if you need further assistance, contact GitHub Support. For more information, see "Creating a support ticket." [Updated: 2022-10-14]
In some cases, GitHub Advanced Security customers who upgrade to GitHub Enterprise Server 3.5 or later may notice that alerts from secret scanning are missing in the web UI and REST API. To ensure the alerts remain visible, do not skip 3.4 when you upgrade from an earlier release to 3.5 or later. A fix is available in the 3.5.5 and 3.6.1 patch releases.
To plan an upgrade through 3.4, see the Upgrade assistant. [Updated: 2022-09-01]
After registering a self-hosted runner with the
--ephemeralparameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17]After upgrading to GitHub Enterprise Server 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
Enterprise Server 3.4.17
Download GitHub Enterprise Server 3.4.17March 02, 2023
š£ This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.
3.4.17: Security fixes
HIGH: A path traversal vulnerability was identified in GitHub Enterprise Server that allowed remote code execution when building a GitHub Pages site. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability was reported via the GitHub Bug Bounty Program and has been assigned CVE-2023-23760. [Updated: 2023-03-10]
3.4.17: Bug fixes
When viewing a list of open sessions for the devices logged into a user account, the GitHub Enterprise Server web UI could display an incorrect location.
In the rare case when primary shards for Elasticsearch were located on a replica node, the
ghe-repl-stopcommand would fail withERROR: Running migrations.
3.4.17: Known issues
On a freshly set up GitHub Enterprise Server instance without any users, an attacker could create the first admin user.
Custom firewall rules are removed during the upgrade process.
Git LFS tracked files uploaded through the web interface are incorrectly added directly to the repository.
When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
After registering a self-hosted runner with the
--ephemeralparameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17]After upgrading to GitHub Enterprise Server 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
In some cases, GitHub Advanced Security customers who upgrade to GitHub Enterprise Server 3.5 or later may notice that alerts from secret scanning are missing in the web UI and REST API. To ensure the alerts remain visible, do not skip 3.4 when you upgrade from an earlier release to 3.5 or later. A fix is available in the 3.5.5 and 3.6.1 patch releases.
To plan an upgrade through 3.4, see the Upgrade assistant. [Updated: 2022-09-01]
Hotpatch upgrades to GitHub Enterprise Server 3.4.9 may fail. Upgrades with the full
.pkgare unaffected. If the upgrade fails for your instance, workaround this issue by connecting to the administrative shell (ssh) and running the following non-interactive command:echo "grub-pc grub-pc/install_devices_empty boolean true" | sudo debconf-set-selectionsIf you're unable to upgrade, or if you need further assistance, contact GitHub Support. For more information, see "Creating a support ticket." [Updated: 2022-10-14]
Enterprise Server 3.4.16
Download GitHub Enterprise Server 3.4.16February 16, 2023
š£ This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.
3.4.16: Security fixes
HIGH: Updated Git to include fixes from 2.39.2, which address CVE-2023-22490 and CVE-2023-23946.
Packages have been updated to the latest security versions.
3.4.16: Known issues
On a freshly set up GitHub Enterprise Server instance without any users, an attacker could create the first admin user.