Information Exposure Affecting golang-github-cli-go-gh-v2 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIANUNSTABLE-GOLANGGITHUBCLIGOGHV2-8444656
  • published30 Nov 2024
  • disclosed27 Nov 2024

Introduced: 27 Nov 2024

NewCVE-2024-53859  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

There is no fixed version for Debian:unstable golang-github-cli-go-gh-v2.

NVD Description

Note: Versions mentioned in the description apply only to the upstream golang-github-cli-go-gh-v2 package and not the golang-github-cli-go-gh-v2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

go-gh is a Go module for interacting with the gh utility and the GitHub API from the command line. A security vulnerability has been identified in go-gh that could leak authentication tokens intended for GitHub hosts to non-GitHub hosts when within a codespace. go-gh sources authentication tokens from different environment variables depending on the host involved: 1. GITHUB_TOKEN, GH_TOKEN for GitHub.com and ghe.com and 2. GITHUB_ENTERPRISE_TOKEN, GH_ENTERPRISE_TOKEN for GitHub Enterprise Server. Prior to version 2.11.1, auth.TokenForHost could source a token from the GITHUB_TOKEN environment variable for a host other than GitHub.com or ghe.com when within a codespace. In version 2.11.1, auth.TokenForHost will only source a token from the GITHUB_TOKEN environment variable for GitHub.com or ghe.com hosts. Successful exploitation could send authentication token to an unintended host. This issue has been addressed in version 2.11.1 and all users are advised to upgrade. Users are also advised to regenerate authentication tokens and to review their personal security log and any relevant audit logs for actions associated with their account or enterprise.