CVE-2024-52308

A security vulnerability has been identified in GitHub CLI that could allow remote code execution (RCE) when users connect to a malicious Codespace SSH server and use the gh codespace ssh or gh codespace logs commands.

Details

The vulnerability stems from the way GitHub CLI handles SSH connection details when executing commands. When developers connect to remote Codespaces, they typically use a SSH server running within a devcontainer, often provided through the default devcontainer image. GitHub CLI retrieves SSH connection details, such as remote username, which is used in executing ssh commands 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.

Remediation and Mitigation

1. Upgrade gh to 2.62.0
2. Exercise caution when using custom devcontainer images, prefer default or pre-built devcontainers from trusted sources.

Successful exploitation could lead to arbitrary code execution on the user's workstation, potentially compromising the user's data and system.

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

CVE-2024-52308 has a CVSS score of 8.0 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.62.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-52308? CVE-2024-52308 is a high-severity command injection vulnerability in github.com/cli/cli/v2 (go), affecting versions <= 2.61.0. It is fixed in 2.62.0. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
2. How severe is CVE-2024-52308? CVE-2024-52308 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2024-52308?
   • github.com/cli/cli/v2 (go) (versions <= 2.61.0)
   • github.com/cli/cli (go) (versions < 2.62.0)
4. Is there a fix for CVE-2024-52308? Yes. CVE-2024-52308 is fixed in 2.62.0. Upgrade to this version or later.
5. Is CVE-2024-52308 exploitable, and should I be worried? Whether CVE-2024-52308 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-52308 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-52308?
   • Upgrade github.com/cli/cli/v2 to 2.62.0 or later
   • Upgrade github.com/cli/cli to 2.62.0 or later

Other vulnerabilities in github.com/cli/cli/v2