Approved changes feed: RSS · Atom
cpe:2.3:a:tg123:sshpiper:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Tg123 (409dd885-607f-5387-92bf-79f4c663a858) |
|---|---|
| Product | Sshpiper (4266fd5c-e051-5971-9283-b242be6ba9a6) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-35175 |
vulnerable | 2026-06-08 06:37:35.380966 |
sshpiper's Enabling of Proxy Protocol without proper feature flagging allows faking source address
MEDIUM (5.3)
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.
Published: 2024-05-14T22:05:11.360Z
Updated: 2024-08-02T03:07:46.846Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.