sshpiper's Enabling of Proxy Protocol without proper feature flagging allows faking source address
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2024-35175
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 04:57 UTC · Revision 1
Source evidence
sshpiper's Enabling of Proxy Protocol without proper feature flagging allows faking source address
core-osv · Original sourcePublished 14 May 2024, 22:05 UTC
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.
osv:CVE-2024-35175
Complete source record
{
"id": "7d968acc54c57290ad918a2c14c762cc83f9955f80ebd7b550c4daef5777eb27",
"url": "https://osv.dev/vulnerability/CVE-2024-35175",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "sshpiper's Enabling of Proxy Protocol without proper feature flagging allows faking source address",
"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.",
"evidence": "osv:CVE-2024-35175",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2024-35175",
"aliases": [
"CVE-2024-35175",
"GHSA-4w53-6jvp-gg52",
"GO-2024-2853"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/tg123/sshpiper",
"type": "GIT",
"events": [
{
"introduced": "319824e5649b1d6072ca61e96261bbded18aa24b"
},
{
"fixed": "70fb830dca26bea7ced772ce5d834a3e88ae7f53"
},
{
"fixed": "2ddd69876a1e1119059debc59fe869cb4e754430"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "1.0.50"
},
{
"fixed": "1.3.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "2ddd69876a1e1119059debc59fe869cb4e754430"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "70fb830dca26bea7ced772ce5d834a3e88ae7f53"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v1.2.8",
"v1.2.7",
"v1.2.6",
"v1.2.5",
"v1.2.4",
"v1.2.3",
"v1.2.2",
"v1.2.1",
"v1.2.0",
"v1.1.22",
"v1.1.4",
"v1.0.105",
"v1.0.101",
"v1.0.96",
"v1.0.94",
"v1.0.83",
"v1.0.80",
"v1.0.78",
"v1.0.72",
"v1.0.62",
"v1.0.50"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-35175.json"
}
}
],
"modified": "2026-10-28T02:30:33.578899023Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/35xxx/CVE-2024-35175.json",
"https://github.com/tg123/sshpiper/security/advisories/GHSA-4w53-6jvp-gg52",
"https://nvd.nist.gov/vuln/detail/CVE-2024-35175",
"https://github.com/tg123/sshpiper/commit/2ddd69876a1e1119059debc59fe869cb4e754430",
"https://github.com/tg123/sshpiper/commit/70fb830dca26bea7ced772ce5d834a3e88ae7f53"
],
"provider_metadata": {
"cwe_ids": [
"CWE-345"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/35xxx/CVE-2024-35175.json"
}
},
"related_cves": [
{
"value": "CVE-2024-35175",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 500412,
"published_at": "2024-05-14T22:05:11.36+00:00"
}