{"answers":{"affected":"3 open source packages ship an affected version, including github.com/tg123/sshpiper.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-35175 exists.","fix":"Upgrade github.com/tg123/sshpiper to 1.3.0 or later.","what":"CVE-2024-35175 is a medium-severity vulnerability in tg123 sshpiper, published on 14 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-35175 and fix it if it is affected.\n\nWhat it is: CVE-2024-35175 is a medium-severity vulnerability in tg123 sshpiper, published on 14 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-35175 exists.\n\nAffected packages and fixed versions:\n- github.com/tg123/sshpiper (Go): affected from 1.0.50; fixed in 1.3.0\n- github.com/tg123/sshpiper (Go): affected from 1.0.50; fixed in 1.3.0\n- github.com/tg123/sshpiper (Go): affected from 1.0.50; fixed in 1.3.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-35175/ (Markdown: https://insights.sbomify.com/CVE-2024-35175/index.md)","id":"CVE-2024-35175","markdown":"https://insights.sbomify.com/CVE-2024-35175/index.md","name":"CVE-2024-35175","record":{"aliases":["GHSA-4w53-6jvp-gg52","GO-2024-2853"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SSH reverse proxy","requires_auth":"none","summary":"Attackers can forge source addresses in sshpiper logs, undermining security monitoring and rate limiting controls.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"sshpiper's Enabling of Proxy Protocol without proper feature flagging allows faking source address","id":"CVE-2024-35175","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":3,"next":{"headline":"REXML contains a denial of service vulnerability","id":"CVE-2024-35176"},"packages":[{"ecosystem":"Go","fixed":["1.3.0"],"introduced":["1.0.50"],"last_affected":[],"package":"github.com/tg123/sshpiper","purl":null,"source":"GHSA-4w53-6jvp-gg52"},{"ecosystem":"Go","fixed":["1.3.0"],"introduced":["1.0.50"],"last_affected":[],"package":"github.com/tg123/sshpiper","purl":"pkg:golang/github.com/tg123/sshpiper","source":"GHSA-4w53-6jvp-gg52"},{"ecosystem":"Go","fixed":["1.3.0"],"introduced":["1.0.50"],"last_affected":[],"package":"github.com/tg123/sshpiper","purl":"pkg:golang/github.com/tg123/sshpiper","source":"GO-2024-2853"}],"prev":{"headline":"WordPress Flo Forms plugin \u003c= 1.0.42 - Broken Access Control vulnerability","id":"CVE-2024-35174"},"products":["sshpiper"],"published":"2024-05-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["tg123"]},"summary":"Attackers can forge source addresses in sshpiper logs, undermining security monitoring and rate limiting controls.","url":"https://insights.sbomify.com/CVE-2024-35175/"}