Echo CSRF bypass in MethodOverride 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, Echo's MethodOverride middleware accepts a safe HTTP method as the override target for a POST request. When MethodOverride is registered before CSRF in the post-routing middleware chain, route selection retains the original state-changing POST handler but the override changes the method before CSRF evaluates it, causing both token validation and Sec-Fetch-Site checks to be skipped. A cross-site exploit requires an authenticated victim and an override value that a browser-submitted request can control, such as the form getter used by the advisory reproducer; the default X-HTTP-Method-Override header getter is not settable by a cross-site form. This issue is fixed in 4.16.0 and 5.4.0.
From the CVE record · GitHub_M
Echo's MethodOverride middleware can cause CSRF checks to be skipped for a state-changing POST handler when it runs before CSRF in the post-routing chain and overrides POST with a safe method. Cross-site exploitation requires an authenticated victim and an override value controllable by a browser-submitted request; the default header getter is not controllable by a cross-site form.
Check Go applications using github.com/labstack/echo/v4 before 4.16.0 or github.com/labstack/echo/v5 from 5.0.0 up to, but not including, 5.4.0.