Zoraxy has an authenticated command injection in the Web SSH feature

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2024-52010: 1.50% estimated exploitation activity in the next 30 days; percentile 74.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A command injection vulnerability in the Web SSH feature allows an authenticated attacker to execute arbitrary commands as root on the host. Details Zoraxy has a Web SSH terminal feature that allows authenticated users to connect to SSH servers from their browsers. In HandleCreateProxySession the request to create an SSH session is handled. After checking for the presence of required parameters, ensuring that the target is not the loopback interface and that there is actually an SSH service running on the target, CreateNewConnection is called: https://github.com/tobychui/zoraxy/blob/e79a70b7acfa45c2445aff9d60e4e7525c89fec8/src/mod/sshprox/sshprox.go#L165-L178 In line 178, the gotty binary is executed running sshCommand from the line above. It contains the user-controlled variable connAddr, which includes the hostname of the SSH server and - if provided - the username. An attacker can exploit the username variable to escape from the bash command and inject arbitrary commands…

Published by the source

12 Nov 2024, 21:28 UTC

Last modified by the source

19 Nov 2024, 19:38 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7hpf-g48v-hw3j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-52010

Advisory: Zoraxy has an authenticated command injection in the Web SSH feature
IDs: CVE-2024-52010, GHSA-7hpf-g48v-hw3j
Record: https://patchnext.com/advisories/cve-2024-52010 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/tobychui/zoraxy 3.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/tobychui/zoraxy: affected >= 2.6.1, < 3.1.3; fixed in 3.1.3

## Suggested inspection (read-only)
- Go github.com/tobychui/zoraxy: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/tobychui/zoraxy.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7hpf-g48v-hw3j (GitHub-reviewed advisory GHSA-7hpf-g48v-hw3j lists affected ranges: Go github.com/tobychui/zoraxy >=2.6.1 <3.1.3)

Commands are suggestions: review each one before running it.