mirror of
https://github.com/carlospolop/hacktricks
synced 2024-11-15 01:17:36 +00:00
GitBook: [master] one page modified
This commit is contained in:
parent
7391119422
commit
c620191fb3
1 changed files with 12 additions and 0 deletions
|
@ -358,3 +358,15 @@ This information includes remote client IP's, session IDs, all request and respo
|
|||
|
||||
![Screenshot 2021-03-30 at 13 19 11](https://user-images.githubusercontent.com/31736688/112974448-2690b000-915b-11eb-896c-f41c27c44286.png)
|
||||
|
||||
## ASPXAUTH Cookie
|
||||
|
||||
ASPXAUTH uses the following info:
|
||||
|
||||
* **`validationKey`** \(string\): hex-encoded key to use for signature validation.
|
||||
* **`decryptionMethod`** \(string\): \(default “AES”\).
|
||||
* **`decryptionIV`** \(string\): hex-encoded initialization vector \(defaults to a vector of zeros\).
|
||||
* **`decryptionKey`** \(string\): hex-encoded key to use for decryption.
|
||||
|
||||
However, some people will use the **default values** of these parameters and will use as **cookie the email of the user**. Therefore, if you can find a web using the **same platform** that is using the ASPXAUTH cookie and you **create a user with the email of the user you want to impersonate** on the server under attack, you may be able to us**e the cookie from the second server in the first one** and impersonate the user.
|
||||
This attacked worked in this [**writeup**](https://infosecwriteups.com/how-i-hacked-facebook-part-two-ffab96d57b19).
|
||||
|
||||
|
|
Loading…
Reference in a new issue