-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
161 additions
and
126 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7391,10 +7391,9 @@ Signed-off-by: Euan Kemp <[email protected]> | |
| 1. Malice initiates an OAuth 2.0 Authorization Code Flow: | ||
| https://hydra/oauth2/auth?client=... | ||
|
|
||
|
|
||
| - Hydra creates the consent request id and an additional CSRF token | ||
| which is stored in the database and the encrypted cookie. Malice | ||
| is not able to see the CSRF token. | ||
| - Hydra creates the consent request id and an additional CSRF token which | ||
| is stored in the database and the encrypted cookie. Malice is not able to | ||
| see the CSRF token. | ||
|
|
||
| 2. Hydra redirects malice to the consent app and appends consent id | ||
| "example-id": https://consent-app/?consent=example-id | ||
|
|
@@ -7669,10 +7668,9 @@ contains this patch does not require any code changes or deployment changes. | |
| 1. Malice initiates an OAuth 2.0 Authorization Code Flow: | ||
| https://hydra/oauth2/auth?client=... | ||
|
|
||
|
|
||
| - Hydra creates the consent request id and an additional CSRF token | ||
| which is stored in the database and the encrypted cookie. Malice | ||
| is not able to see the CSRF token. | ||
| - Hydra creates the consent request id and an additional CSRF token which | ||
| is stored in the database and the encrypted cookie. Malice is not able to | ||
| see the CSRF token. | ||
|
|
||
| 2. Hydra redirects malice to the consent app and appends consent id | ||
| "example-id": https://consent-app/?consent=example-id | ||
|
|
@@ -7965,10 +7963,9 @@ Signed-off-by: Euan Kemp <[email protected]> | |
| 1. Malice initiates an OAuth 2.0 Authorization Code Flow: | ||
| https://hydra/oauth2/auth?client=... | ||
|
|
||
|
|
||
| - Hydra creates the consent request id and an additional CSRF token | ||
| which is stored in the database and the encrypted cookie. Malice | ||
| is not able to see the CSRF token. | ||
| - Hydra creates the consent request id and an additional CSRF token which | ||
| is stored in the database and the encrypted cookie. Malice is not able to | ||
| see the CSRF token. | ||
|
|
||
| 2. Hydra redirects malice to the consent app and appends consent id | ||
| "example-id": https://consent-app/?consent=example-id | ||
|
|
@@ -8170,10 +8167,9 @@ contains this patch does not require any code changes or deployment changes. | |
| 1. Malice initiates an OAuth 2.0 Authorization Code Flow: | ||
| https://hydra/oauth2/auth?client=... | ||
|
|
||
|
|
||
| - Hydra creates the consent request id and an additional CSRF token | ||
| which is stored in the database and the encrypted cookie. Malice | ||
| is not able to see the CSRF token. | ||
| - Hydra creates the consent request id and an additional CSRF token which | ||
| is stored in the database and the encrypted cookie. Malice is not able to | ||
| see the CSRF token. | ||
|
|
||
| 2. Hydra redirects malice to the consent app and appends consent id | ||
| "example-id": https://consent-app/?consent=example-id | ||
|
|
||
Oops, something went wrong.