What is CVE-2024-34713?

CVE-2024-34713 is a low-severity command injection vulnerability in github.com/cea-hpc/sshproxy (go), affecting versions <= 1.6.2. It is fixed in 1.6.3. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.

How severe is CVE-2024-34713?

CVE-2024-34713 has a CVSS score of 3.5 (Low). 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.

Which versions of github.com/cea-hpc/sshproxy are affected by CVE-2024-34713?

github.com/cea-hpc/sshproxy (go) versions <= 1.6.2 is affected.

Is there a fix for CVE-2024-34713?

Yes. CVE-2024-34713 is fixed in 1.6.3. Upgrade to this version or later.

Is CVE-2024-34713 exploitable, and should I be worried?

Whether CVE-2024-34713 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.

What actually determines whether CVE-2024-34713 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.

How do I fix CVE-2024-34713?

Upgrade github.com/cea-hpc/sshproxy to 1.6.3 or later.

CVE-2024-34713 in github.com/cea-hpc/sshproxy

Q: How severe is CVE-2024-34713?

CVE-2024-34713 has a CVSS score of 3.5 (Low). 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.

Q: Which versions of github.com/cea-hpc/sshproxy are affected by CVE-2024-34713?

github.com/cea-hpc/sshproxy (go) versions <= 1.6.2 is affected.

Q: Is there a fix for CVE-2024-34713?

Yes. CVE-2024-34713 is fixed in 1.6.3. Upgrade to this version or later.

Q: Is CVE-2024-34713 exploitable, and should I be worried?

Whether CVE-2024-34713 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.

Q: What actually determines whether CVE-2024-34713 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.

Q: How do I fix CVE-2024-34713?

Upgrade github.com/cea-hpc/sshproxy to 1.6.3 or later.

Summary

sshproxy vulnerable to SSH option injection

Workarounds

The only workaround is to use the force_command option in sshproxy.yaml, but it's rarely relevant.

References

Impact

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.

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-34713 has a CVSS score of 3.5 (Low). 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 (1.6.3); upgrading removes the vulnerable code path.

Affected versions

github.com/cea-hpc/sshproxy (<= 1.6.2)

Security releases

github.com/cea-hpc/sshproxy → 1.6.3 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The problem is patched starting on version 1.6.3

Frequently Asked Questions

What is CVE-2024-34713? CVE-2024-34713 is a low-severity command injection vulnerability in github.com/cea-hpc/sshproxy (go), affecting versions <= 1.6.2. It is fixed in 1.6.3. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
How severe is CVE-2024-34713? CVE-2024-34713 has a CVSS score of 3.5 (Low). 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.
Which versions of github.com/cea-hpc/sshproxy are affected by CVE-2024-34713? github.com/cea-hpc/sshproxy (go) versions <= 1.6.2 is affected.
Is there a fix for CVE-2024-34713? Yes. CVE-2024-34713 is fixed in 1.6.3. Upgrade to this version or later.
Is CVE-2024-34713 exploitable, and should I be worried? Whether CVE-2024-34713 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
What actually determines whether CVE-2024-34713 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.
How do I fix CVE-2024-34713? Upgrade github.com/cea-hpc/sshproxy to 1.6.3 or later.