نسخههای متأثر
- نسخههای متأثر
- >= 0.30.3, < 0.34.1
- نسخهٔ اصلاحشده
- 0.34.1
بهرهبرداری
شرح آسیبپذیری
Impact
fosite#400 (released as v0.30.2) introduced a new feature for handling redirect URLs pointing to loopback interfaces (rfc8252#section-7.3). As part of that change new behavior was introduced which failed to respect the redirect URL's (only for loopback interfaces!) query parameters
Registering a client with allowed redirect URL
http://127.0.0.1/callbackPerforming OAuth2 flow and requesting redirect URL
http://127.0.0.1/callback?bar=fooInstead of an error, the browser is redirected to
http://127.0.0.1/callback?bar=foowith a potentially successful OAuth2 response.
as well as the host parameter (as long as the host is a loopback interface):
Registering a client with allowed redirect URL
https://example.com/callbackPerforming OAuth2 flow and requesting redirect URL
http://127.0.0.1/callbackInstead of an error, the browser is redirected to
http://127.0.0.1/callbackwith a potentially successful OAuth2 response.
These bugs are only applicable in scenarios where the attacker has control over the loopback interface (localhost, 127.0.0.1, [::1]) where the browser performing the OAuth2 flow is running.
پیوندها
- https://github.com/advisories/GHSA-rfq3-w54c-f9q5
- https://github.com/ory/fosite
- https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf
- https://github.com/ory/fosite/pull/400
- https://github.com/ory/fosite/security/advisories/GHSA-rfq3-w54c-f9q5
- https://nvd.nist.gov/vuln/detail/CVE-2020-15233
گزارشدهندگان
- mitar
- aeneasr

