CVE-2024-35175 json
sshpiper's Enabling of Proxy Protocol without proper feature flagging allows faking source address
published 2024-05-14 2 y ago modified 2026-09-10 1 mo ago also GHSA-4w53-6jvp-gg52 , GO-2024-2853 , EUVD-2024-1427
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/tg123/sshpiper 1.3.0
- tg123 sshpiper 1.3.0
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/tg123/sshpiper | >=1.0.50, <1.3.0 |
1.3.0 |
Affected products
- tg123 sshpiper
Classification
- Weakness
-
- CWE-345 Insufficient Verification of Data Authenticity
References
-
github.com
/tg123/sshpiper/commit/2ddd69876a1e1119059debc59fe869cb4e754430
web, patch
-
github.com
/tg123/sshpiper/commit/70fb830dca26bea7ced772ce5d834a3e88ae7f53
web, patch
-
github.com
/tg123/sshpiper/security/advisories/GHSA-4w53-6jvp-gg52
web, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-35175
advisory
-
github.com
/tg123/sshpiper
package
Sources
- CVE List CVE-2024-35175
- GitHub Advisory GHSA-4w53-6jvp-gg52
- NVD CVE-2024-35175
- OSV GO-2024-2853
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.