Termix: Authenticated SSRF via `/homepage/proxy` โ No Destination Allowlist
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. From 2.5.0 until 2.5.1, the /homepage/proxy endpoint accepts an authenticated user's url query parameter and passes it to http.get or https.get without destination restrictions. In src/backend/database/routes/homepage-proxy-routes.ts, new URL performs only syntactic validation, allowing requests to loopback, RFC1918, link-local, and cloud metadata destinations. The endpoint returns the complete fetched JSON response, so a low-privilege or self-registered account can exfiltrate internal service data and cloud credentials. This issue is fixed in version 2.5.1.
Text from CVE List
Affected versions 1
- Termixaffected: >= 2.5.0, < 2.5.1CVE List
References 5
- github.com/Termix-SSH/Termix/commit/4b2a60a854281d0e12e7c9bcde71854a81999ea0Fixvia CVE List
- github.com/Termix-SSH/Termix/commit/ddbdd5c437c2296607dfaa4265d6f63fbc1ca92eFixvia CVE List
- github.com/Termix-SSH/Termix/releases/tag/release-2.5.1-tagFixvia CVE List
- github.com/Termix-SSH/Termix/security/advisories/GHSA-mwr3-35ph-pjqgExploitvia CVE List
- github.com/Termix-SSH/Termix/pull/1067Referencevia CVE List