What is CVE-2024-35175?

CVE-2024-35175 is a medium-severity security vulnerability in github.com/tg123/sshpiper (go), affecting versions >= 1.0.50, < 1.3.0. It is fixed in 1.3.0.

How severe is CVE-2024-35175?

CVE-2024-35175 has a CVSS score of 5.3 (Medium). 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/tg123/sshpiper are affected by CVE-2024-35175?

github.com/tg123/sshpiper (go) versions >= 1.0.50, < 1.3.0 is affected.

Is there a fix for CVE-2024-35175?

Yes. CVE-2024-35175 is fixed in 1.3.0. Upgrade to this version or later.

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

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

CVE-2024-35175 in github.com/tg123/sshpiper

Q: How severe is CVE-2024-35175?

CVE-2024-35175 has a CVSS score of 5.3 (Medium). 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/tg123/sshpiper are affected by CVE-2024-35175?

github.com/tg123/sshpiper (go) versions >= 1.0.50, < 1.3.0 is affected.

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

Yes. CVE-2024-35175 is fixed in 1.3.0. Upgrade to this version or later.

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

Whether CVE-2024-35175 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-35175 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-35175?

Upgrade github.com/tg123/sshpiper to 1.3.0 or later.

Summary

sshpiper's enabling of proxy protocol without proper feature flagging allows faking source address

The way the proxy protocol listener is implemented in sshpiper can allow an attacker to forge their connecting address.

Details

This commit added the proxy protocol listener as the only listener in sshpiper, with no option to toggle this functionality off. This means that any connection that sshpiper is directly (or in some cases indirectly) exposed to can use proxy protocol to forge its source address.

PoC

You can use a configuration like this in HAProxy:

listen w-send-proxy
    mode tcp
    log global
    option tcplog
    bind *:27654
    tcp-request connection set-src ipv4(1.1.1.1)
    server app1 ssh-piper-hostname:22 send-proxy

When connecting through HAProxy, sshpiper will log connections as originating from 1.1.1.1. The proxy protocol data is designed to survive multiple load balancers or proxies and pass through to sshpiper at the end, so it should only be enabled trusted environments. This should be behind a configuration option or startup flag to prevent abuse when public connections can be made to sshpiper.

This is also backed up by the specification for proxy protocol:

The receiver MUST be configured to only receive the protocol described in this
specification and MUST not try to guess whether the protocol header is present
or not. This means that the protocol explicitly prevents port sharing between
public and private access. Otherwise it would open a major security breach by
allowing untrusted parties to spoof their connection addresses. The receiver
SHOULD ensure proper access filtering so that only trusted proxies are allowed
to use this protocol.

Impact

Any users of sshpiper who need logs from it for whitelisting/rate limiting/security investigations could have them become much less useful if an attacker is sending a spoofed source address.

CVE-2024-35175 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. 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.3.0); upgrading removes the vulnerable code path.

Affected versions

github.com/tg123/sshpiper (>= 1.0.50, < 1.3.0)

Security releases

github.com/tg123/sshpiper → 1.3.0 (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

Upgrade github.com/tg123/sshpiper to 1.3.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-35175? CVE-2024-35175 is a medium-severity security vulnerability in github.com/tg123/sshpiper (go), affecting versions >= 1.0.50, < 1.3.0. It is fixed in 1.3.0.
How severe is CVE-2024-35175? CVE-2024-35175 has a CVSS score of 5.3 (Medium). 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/tg123/sshpiper are affected by CVE-2024-35175? github.com/tg123/sshpiper (go) versions >= 1.0.50, < 1.3.0 is affected.
Is there a fix for CVE-2024-35175? Yes. CVE-2024-35175 is fixed in 1.3.0. Upgrade to this version or later.
Is CVE-2024-35175 exploitable, and should I be worried? Whether CVE-2024-35175 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-35175 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-35175? Upgrade github.com/tg123/sshpiper to 1.3.0 or later.