Ech0 before 4.7.3 OAuth Redirect URI Validation Bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| lin-snow | Ech0 | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Ech0 | Ech0 |
|
||||||||||||
| Lin-snow | Ech0 |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.321% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Lin-snow
Lin-snow ech0 |
|
| Vendors & Products |
Lin-snow
Lin-snow ech0 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Ech0 through 4.5.6 contains an OAuth redirect URI validation vulnerability in parseAndValidateClientRedirect (internal/service/auth/auth.go) that compares only the scheme and host of the client-supplied redirect_uri against the admin-configured allowlist, ignoring path, query, and fragment components. The redirect_uri is embedded into the signed state JWT at login time without validation. An attacker can craft a redirect_uri whose host matches an allowed origin but whose path is attacker-influenced; after the OAuth exchange the victim is redirected to that path with a one-time exchange code in the query string. If the code leaks (e.g., via Referer, analytics, or an open redirect on that host), the attacker can trade it at the public POST /api/auth/exchange endpoint for the victim's access and refresh tokens. Fixed in 4.7.3. | |
| Title | Ech0 before 4.7.3 OAuth Redirect URI Validation Bypass | |
| First Time appeared |
Ech0
Ech0 ech0 |
|
| Weaknesses | CWE-601 | |
| CPEs | cpe:2.3:a:ech0:ech0:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Ech0
Ech0 ech0 |
|
| References |
| |
| Metrics |
cvssV3_1
|