CVE-2024-35175

{"id": "CVE-2024-35175", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "published": "2024-05-14T22:15:10.213", "references": [{"url": "https://github.com/tg123/sshpiper/commit/2ddd69876a1e1119059debc59fe869cb4e754430", "source": "security-advisories@github.com"}, {"url": "https://github.com/tg123/sshpiper/commit/70fb830dca26bea7ced772ce5d834a3e88ae7f53", "source": "security-advisories@github.com"}, {"url": "https://github.com/tg123/sshpiper/security/advisories/GHSA-4w53-6jvp-gg52", "source": "security-advisories@github.com"}, {"url": "https://github.com/tg123/sshpiper/commit/2ddd69876a1e1119059debc59fe869cb4e754430", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/tg123/sshpiper/commit/70fb830dca26bea7ced772ce5d834a3e88ae7f53", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/tg123/sshpiper/security/advisories/GHSA-4w53-6jvp-gg52", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-345"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "sshpiper es un proxy inverso para sshd. A partir de la versi\u00f3n 1.0.50 y antes de la versi\u00f3n 1.3.0, la forma en que se implementa el escucha del protocolo proxy en sshpiper puede permitir que un atacante falsifique su direcci\u00f3n de conexi\u00f3n. El commit 2ddd69876a1e1119059debc59fe869cb4e754430 agreg\u00f3 el escucha del protocolo proxy como el \u00fanico escucha en sshpiper, sin opci\u00f3n para desactivar esta funcionalidad. Esto significa que cualquier conexi\u00f3n a la que sshpiper est\u00e9 expuesto directamente (o en algunos casos indirectamente) puede utilizar el protocolo proxy para falsificar su direcci\u00f3n de origen. Cualquier usuario de sshpiper que necesite registros del mismo para incluirlos en listas blancas, limitar la velocidad o realizar investigaciones de seguridad podr\u00eda volverlos mucho menos \u00fatiles si un atacante env\u00eda una direcci\u00f3n de origen falsificada. La versi\u00f3n 1.3.0 contiene un parche para el problema."}], "lastModified": "2024-11-21T09:19:52.233", "sourceIdentifier": "security-advisories@github.com"}