CVE-2024-35175 sshpiper's Enabling of Proxy Protocol without proper feature flagging allows faking source address
Attackers can forge source addresses in sshpiper logs, undermining security monitoring and rate limiting controls.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-35175?
CVE-2024-35175 is a medium-severity vulnerability in tg123 sshpiper, published on 14 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
sshpiper is a reverse proxy for sshd. Starting in version 1.0.50 and prior to version 1.3.0, the way the proxy protocol listener is implemented in sshpiper can allow an attacker to forge their connecting address. Commit 2ddd69876a1e1119059debc59fe869cb4e754430 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. 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. Version 1.3.0 contains a patch for the issue.
Weakness: CWE-345
Which versions are affected by CVE-2024-35175?
3 open source packages ship an affected version, including github.com/tg123/sshpiper.
| Package | Affected | Fixed in |
|---|---|---|
github.com/tg123/sshpiper Go | From 1.0.50 | 1.3.0 |
github.com/tg123/sshpiper Go | From 1.0.50 | 1.3.0 |
github.com/tg123/sshpiper Go | From 1.0.50 | 1.3.0 |
How do I fix CVE-2024-35175?
Upgrade github.com/tg123/sshpiper to 1.3.0 or later.
Is CVE-2024-35175 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-35175 exists.
Sources
Also known as GHSA-4w53-6jvp-gg52, GO-2024-2853.