Echo open redirect in trailing-slash middleware
labstack echo
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/labstack/echo/v5 Go |
|
|
| github.com/labstack/echo/v4 Go |
|
|
labstack echo
| Product | Affected | Fixed in |
|---|---|---|
| github.com/labstack/echo/v5 Go |
|
|
| github.com/labstack/echo/v4 Go |
|
|
Echo is a Go web framework. Prior to 4.16.0 and 5.4.0, sanitizeURI checks only the first two bytes of a redirect target before deciding whether it begins with an absolute-path separator pair. When AddTrailingSlash or RemoveTrailingSlash is configured with a redirect status, a slash, TAB, separator path form can evade the guard, be emitted in the Location header, and be normalized by a browser into an attacker-controlled host. This issue is fixed in 4.16.0 and 5.4.0.
From the CVE record · GitHub_M
Echo’s sanitizeURI can fail to reject a crafted redirect target when AddTrailingSlash or RemoveTrailingSlash is configured with a redirect status. A browser following the resulting Location header may be sent to an attacker-controlled host.
Teams using Go package github.com/labstack/echo/v4 before 4.16.0 or github.com/labstack/echo/v5 before 5.4.0 should check their deployments.