Echo reflected XSS in JSONP callbacks
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, Context.JSONP and Context.JSONPBlob concatenate an unvalidated callback value into a JavaScript response. A route that passes attacker-controlled input as the callback can return executable script syntax, allowing reflected cross-site scripting when a user loads the crafted response. The vulnerable jsonPBlob path performs no callback validation or escaping, and exploitation requires an application route that exposes attacker control over the callback argument. This issue is fixed in 4.16.0 and 5.4.0.
From the CVE record · GitHub_M
Echo's Context.JSONP and Context.JSONPBlob can include an unvalidated callback in a JavaScript response. If an application route lets an attacker control that callback, a user loading a crafted response can trigger reflected cross-site scripting.
Check applications using Go github.com/labstack/echo/v4 before 4.16.0 or github.com/labstack/echo/v5 before 5.4.0.