Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-4w53-6jvp-gg52

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

CVSS 5.3 MediumEPSS 0.0026 · 17th percentile

Published by the GitHub Advisory Database at 14 May 2024, 22:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/tg123/sshpiperGo>=1.0.50, <1.3.01.3.0
Identifiers
GHSA-4w53-6jvp-gg52 · CVE-2024-35175 · GO-2024-2853
Weakness (CWE)
CWE-345
Tags
Published
14 May 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

sshpiper versions 1.0.50 up to but not including 1.3.0 always accept the proxy protocol listener, with no option to disable it. An attacker who can connect directly to sshpiper, or indirectly in some setups, can send proxy protocol headers to make connections appear to come from an arbitrary source address in its logs. Upgrade to sshpiper 1.3.0. The source gives no workaround besides upgrading.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0026, the 17th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:15 UTC First seen by agentprime
  2. 31 Oct 2026, 14:15 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.