---
id: CVE-2024-35175
aliases:
  - GHSA-4w53-6jvp-gg52
  - GO-2024-2853
title: >-
  sshpiper's enabling of proxy protocol without proper feature flagging allows
  faking source address
summary: >-
  sshpiper's enabling of proxy protocol without proper feature flagging allows
  faking source address
severity: medium
cvss: 5.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'
vendor: tg123
product: github.com/tg123/sshpiper
ecosystem: go
affected:
  - 'github.com/tg123/sshpiper >= 1.0.50, < 1.3.0'
patched:
  - github.com/tg123/sshpiper 1.3.0
published: '2024-05-14'
updated: '2026-09-10'
sourceUpdated: '2026-09-10T03:50:13.239534206Z'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/GHSA-4w53-6jvp-gg52'
references:
  - url: 'https://github.com/tg123/sshpiper/security/advisories/GHSA-4w53-6jvp-gg52'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2024-35175'
  - url: >-
      https://github.com/tg123/sshpiper/commit/2ddd69876a1e1119059debc59fe869cb4e754430
  - url: >-
      https://github.com/tg123/sshpiper/commit/70fb830dca26bea7ced772ce5d834a3e88ae7f53
  - url: 'https://github.com/tg123/sshpiper'
tags:
  - osv
  - go
epss: 0.0026
epssPercentile: 0.18005
ingestedAt: '2026-09-12T03:13:01.754Z'
---

## Overview

### Summary

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

### Details

[This commit](https://github.com/tg123/sshpiper/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.

### 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](https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt):

> 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.

## Affected packages

- `github.com/tg123/sshpiper >= 1.0.50, < 1.3.0`

## Remediation

Upgrade to a patched release:

- `github.com/tg123/sshpiper 1.3.0`