Echo Proxyでルート認可を回避される脆弱性、修正版あり
Summary
Go製のWebフレームワークEchoのProxy middlewareに、ルートごとの認証・認可をすり抜けられる脆弱性が見つかりました。Echoをリバースプロキシや社内ゲートウェイとして使い、認可をEchoのルートだけに頼っている組織は影響を受けます。4.16.1または5.4.1へ更新し、バックエンド側にも独立した認可があるかを確認してください。
AI summary
Written by an external AI model and may contain mistakes. Check the original description and references below before acting on it.
Go製のWebフレームワークEchoのProxy middlewareに、ルートごとの認証・認可をすり抜けられる脆弱性が見つかりました。Echoをリバースプロキシや社内ゲートウェイとして使い、認可をEchoのルートだけに頼っている組織は影響を受けます。4.16.1または5.4.1へ更新し、バックエンド側にも独立した認可があるかを確認してください。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| labstack | echo | — | — |
| go | github.com/labstack/echo/v4 |
≥ 4.0.0, < 4.16.1 |
4.16.1 |
| go | github.com/labstack/echo/v5 |
≥ 5.0.0, < 5.4.1 |
5.4.1 |
Original description The description as published by the source.
Impact
Echo's Proxy middleware selected a raw tunnel when the client requested a WebSocket upgrade, before validating whether the configured upstream accepted it. If the upstream returned an ordinary HTTP response and kept the connection alive, subsequent HTTP requests on that connection were forwarded directly to the same upstream without passing through Echo's router or route-specific middleware.
This can bypass authentication or authorization enforced only at Echo's routes. Exploitation requires an accessible proxy route, an upstream that rejects the upgrade without closing the connection, and a target resource on that upstream without independent authorization. The issue does not provide arbitrary-host proxying or bypass the upstream's own authentication.
Affected versions and patch
The raw proxy implementation is present throughout the v4 and v5 release lines up to v4.16.0 and v5.4.0. Runtime reproductions confirmed v4.15.0, v4.16.0, v5.0.0 and v5.4.0; source history also shows the missing upgrade-response validation in v4.0.0.
Upgrade to v4.16.1 or v5.4.1. The patch routes WebSocket upgrades through Go's HTTP reverse proxy and enters a tunnel only after a valid upstream upgrade response. Rejected upgrades remain ordinary HTTP requests.
Fix commits: v4, [v5](https:/…
Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory