Echo: CSRF Protection Bypass via MethodOverride Rewriting POST to Safe Method
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| labstack | echo | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Labstack | Echo |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-r7w9-592q-9vg4 | Echo has CSRF Protection Bypass via MethodOverride Rewriting POST to Safe Method |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.163% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-807 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Labstack
Labstack echo |
|
| Vendors & Products |
Labstack
Labstack echo |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Echo: CSRF Protection Bypass via MethodOverride Rewriting POST to Safe Method | |
| Weaknesses | CWE-352 | |
| References |
|
|
| Metrics |
cvssV3_1
|