Description (CNA)
n8n before 1.123.69, 2.33.4, and 2.34.1 contains an SSRF protection bypass in the OAuth2 credential authorization-code-to-access-token exchange. While OAuth2 discovery and dynamic-client-registration requests use n8n's SSRF-protected HTTP client, the token exchange uses a separate client with no SSRF guard. A user with credential-creation permissions can set the access-token URL to an internal address and complete the OAuth2 flow, causing n8n to send a fixed-shape token-exchange POST to that target and reflect its response body back to the attacker (limited to what the target returns to this specific request).
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| n8n-io / n8n | affected 0 before 1.123.69; unaffected 1.123.69 |
| n8n-io / n8n | affected 2.34.0 before 2.34.1; unaffected 2.34.1 |
| n8n-io / n8n | affected 2.0.0 before 2.33.4; unaffected 2.33.4 |
CWE
CWE-918
References
- https://github.com/n8n-io/n8n/security/advisories/GHSA-c4f6-59xq-95ww
- https://www.vulncheck.com/advisories/n8n-before-ssrf-protection-bypass-via-oauth2
ADP enrichment
No English description supplied.
No references supplied.