sshproxy is used on a gateway to transparently proxy a user SSH connection on the gateway to an internal host via SSH. Prior to version 1.6.3, any user authorized to connect to a ssh server using sshproxy can inject options to the ssh command executed by sshproxy. All versions of sshproxy are impacted. The problem is patched starting in version 1.6.3. The only workaround is to use the force_command option in sshproxy.yaml, but it's rarely relevant.
CVE-2024-34713
LOWNVD 3.53.5—
EchelonGraph scoreMEDIUM confidence
This low-severity CVE scores 3.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 42% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
3.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.5
- EG Score
- 3.5(medium)
- EPSS
- 33.6%
- KEV
- Not listed
Published
May 14, 2024
Last Modified
April 15, 2026
References (4)
- security-advisories@githubhttps://github.com/cea-hpc/sshproxy/commit/f7eabd05d5f0f951e160293692327cad9a7d9580
- security-advisories@githubhttps://github.com/cea-hpc/sshproxy/security/advisories/GHSA-jmqp-37m5-49wh
- af854a3a-2127-422b-91ae-364da2661108https://github.com/cea-hpc/sshproxy/commit/f7eabd05d5f0f951e160293692327cad9a7d9580
- af854a3a-2127-422b-91ae-364da2661108https://github.com/cea-hpc/sshproxy/security/advisories/GHSA-jmqp-37m5-49wh
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/cea-hpc/sshproxy | — | 1.6.3 | — |
Frequently asked(5)
What is CVE-2024-34713?
CVE-2024-34713 is a low vulnerability published on May 14, 2024. sshproxy is used on a gateway to transparently proxy a user SSH connection on the gateway to an internal host via SSH. Prior to version 1.6.3, any user authorized to connect to a ssh server using sshproxy can inject options to the ssh command executed by sshproxy. All versions of sshproxy are…
When was CVE-2024-34713 disclosed?
CVE-2024-34713 was first published in the National Vulnerability Database on May 14, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-34713 actively exploited?
CVE-2024-34713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-34713?
CVE-2024-34713 has a CVSS v3 base score of 3.5 (NVD).
How do I remediate CVE-2024-34713?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-34713, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-34713
Is Your Infrastructure Affected by CVE-2024-34713?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.