gh - Debian Package Tracker

general

source: gh (main)
version: 2.46.0-3
maintainer: Debian Go Packaging Team (DMD)
uploaders: Loren M. Lang [DMD] – Otto Kekäläinen [DMD]
arch: any
std-ver: 4.6.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

old-bpo: 2.18.1+dfsg1-1~bpo11+1
stable: 2.23.0+dfsg1-1
testing: 2.46.0-3
unstable: 2.46.0-3

versioned links

2.18.1+dfsg1-1~bpo11+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.23.0+dfsg1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.46.0-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

action needed

A new upstream version is available: 2.74.1 high

A new upstream version 2.74.1 is available, you should consider packaging it.

Created: 2024-04-04 Last update: 2025-06-14 21:30

3 security issues in bookworm high

There are 3 open security issues in bookworm.

1 important issue:

CVE-2024-52308: The GitHub CLI version 2.6.1 and earlier are vulnerable to remote code execution through a malicious codespace SSH server when using `gh codespace ssh` or `gh codespace logs` commands. This has been patched in the cli v2.62.0. Developers connect to remote codespaces through an SSH server running within the devcontainer, which is generally provided through the [default devcontainer image]( https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-... https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers#using-the-default-dev-container-configuration) . GitHub CLI [retrieves SSH connection details]( https://github.com/cli/cli/blob/30066b0042d0c5928d959e288144300cb28196c9/internal/codespaces/rpc/inv... https://github.com/cli/cli/blob/30066b0042d0c5928d959e288144300cb28196c9/internal/codespaces/rpc/invoker.go#L230-L244 ), such as remote username, which is used in [executing `ssh` commands]( https://github.com/cli/cli/blob/e356c69a6f0125cfaac782c35acf77314f18908d/pkg/cmd/codespace/ssh.go#L2... https://github.com/cli/cli/blob/e356c69a6f0125cfaac782c35acf77314f18908d/pkg/cmd/codespace/ssh.go#L263 ) for `gh codespace ssh` or `gh codespace logs` commands. This exploit occurs when a malicious third-party devcontainer contains a modified SSH server that injects `ssh` arguments within the SSH connection details. `gh codespace ssh` and `gh codespace logs` commands could execute arbitrary code on the user's workstation if the remote username contains something like `-oProxyCommand="echo hacked" #`. The `-oProxyCommand` flag causes `ssh` to execute the provided command while `#` shell comment causes any other `ssh` arguments to be ignored. In `2.62.0`, the remote username information is being validated before being used.

2 issues left for the package maintainer to handle:

CVE-2024-53858: (needs triaging) The gh cli is GitHub’s official command line tool. A security vulnerability has been identified in the GitHub CLI that could leak authentication tokens when cloning repositories containing `git` submodules hosted outside of GitHub.com and ghe.com. This vulnerability stems from several `gh` commands used to clone a repository with submodules from a non-GitHub host including `gh repo clone`, `gh repo fork`, and `gh pr checkout`. These GitHub CLI commands invoke git with instructions to retrieve authentication tokens using the `credential.helper` configuration variable for any host encountered. Prior to version `2.63.0`, hosts other than GitHub.com and ghe.com are treated as GitHub Enterprise Server hosts and have tokens sourced from the following environment variables before falling back to host-specific tokens stored within system-specific secured storage: 1. `GITHUB_ENTERPRISE_TOKEN`, 2. `GH_ENTERPRISE_TOKEN` and 3. `GITHUB_TOKEN` when the `CODESPACES` environment variable is set. The result being `git` sending authentication tokens when cloning submodules. In version `2.63.0`, these GitHub CLI commands will limit the hosts for which `gh` acts as a credential helper to source authentication tokens. Additionally, `GITHUB_TOKEN` will only be used for GitHub.com and ghe.com. Users are advised to upgrade. Additionally users are advised to revoke authentication tokens used with the GitHub CLI and to review their personal security log and any relevant audit logs for actions associated with their account or enterprise
CVE-2024-54132: (needs triaging) The GitHub CLI is GitHub’s official command line tool. A security vulnerability has been identified in GitHub CLI that could create or overwrite files in unintended directories when users download a malicious GitHub Actions workflow artifact through gh run download. This vulnerability stems from a GitHub Actions workflow artifact named .. when downloaded using gh run download. The artifact name and --dir flag are used to determine the artifact’s download path. When the artifact is named .., the resulting files within the artifact are extracted exactly 1 directory higher than the specified --dir flag value. This vulnerability is fixed in 2.63.1.

You can find information about how to handle these issues in the security team's documentation.

Created: 2024-11-18 Last update: 2025-02-27 05:02

2 new commits since last upload, is it time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit f42f34ae1ad2f35f239453f940ed343b30358025
Author: Otto Kekäläinen <otto@debian.org>
Date:   Mon Jan 13 19:54:47 2025 -0800

    Stop polluting upstream file paths and put build artifacts in debian/build

commit 0861af5eb85356d67cf7e0ba7de011b93c3439ed
Author: Otto Kekäläinen <otto@debian.org>
Date:   Mon Jan 13 19:52:14 2025 -0800

    Add minimal gbp.conf so that it is explicit what settings this repo has
    
    The repository was already using pristine-tar, so include it in the
    configuration to next upstream import does not accidentally omit it.
    Also configure the upstream tag format and enforce that the Debian
    maintainer signs tags.
    
    This is not yet the ideal gbp.conf, just the bare minimum for next
    upstream import to be consistent. Branches should be switched to DEP-14
    later when the Go team rolls out workflow updates.

Created: 2025-01-19 Last update: 2025-06-15 00:01

debian/patches: 1 patch to forward upstream low

Among the 7 debian patches available in version 2.46.0-3 of the package, we noticed the following issues:

1 patch where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2024-02-29 Last update: 2025-01-13 15:32

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.2 instead of 4.6.2).

Created: 2024-04-07 Last update: 2025-02-27 13:25

news

[rss feed]

[2025-01-15] gh 2.46.0-3 MIGRATED to testing (Debian testing watch)
[2025-01-13] Accepted gh 2.46.0-3 (source) into unstable (Otto Kekäläinen)
[2025-01-02] gh 2.46.0-2 MIGRATED to testing (Debian testing watch)
[2024-12-30] Accepted gh 2.46.0-2 (source) into unstable (Santiago Vila)
[2024-04-23] gh 2.46.0-1 MIGRATED to testing (Debian testing watch)
[2024-03-27] Accepted gh 2.46.0-1 (source) into unstable (Anthony Fok)
[2024-03-05] Accepted gh 2.45.0-1 (source) into unstable (Anthony Fok)
[2024-03-05] gh 2.44.1-2 MIGRATED to testing (Debian testing watch)
[2024-02-29] Accepted gh 2.44.1-2 (source) into unstable (Shengjing Zhu)
[2024-02-22] gh 2.44.1-1 MIGRATED to testing (Debian testing watch)
[2024-02-19] Accepted gh 2.44.1-1 (source) into unstable (Anthony Fok)
[2024-02-11] gh 2.43.1-1 MIGRATED to testing (Debian testing watch)
[2024-02-07] Accepted gh 2.43.1-1 (source) into unstable (Anthony Fok)
[2024-01-27] gh 2.42.1-1 MIGRATED to testing (Debian testing watch)
[2024-01-24] Accepted gh 2.42.1-1 (source) into unstable (Anthony Fok)
[2024-01-02] gh 2.40.1+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2024-01-02] gh 2.40.1+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2024-01-02] gh 2.40.1+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2023-12-27] Accepted gh 2.40.1+dfsg1-1 (source) into unstable (Anthony Fok)
[2023-12-07] gh 2.35.0-1 MIGRATED to testing (Debian testing watch)
[2023-12-04] Accepted gh 2.35.0-1 (source) into unstable (Anthony Fok)
[2023-11-04] gh 2.30.0-2 MIGRATED to testing (Debian testing watch)
[2023-10-30] Accepted gh 2.30.0-2 (source) into unstable (Nilesh Patra)
[2023-10-18] gh 2.30.0-1 MIGRATED to testing (Debian testing watch)
[2023-10-15] Accepted gh 2.30.0-1 (source) into unstable (Anthony Fok)
[2023-07-07] gh 2.27.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2023-07-07] gh 2.27.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2023-07-07] gh 2.27.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2023-07-04] Accepted gh 2.27.0+dfsg1-1 (source) into unstable (Anthony Fok)
[2023-07-03] Accepted gh 2.24.3+dfsg1-1 (source) into unstable (Anthony Fok)

bugs [bug history graph]

all: 0

links

homepage
lintian
buildd: logs, checks, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
screenshots
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.46.0-3