Fix link and typo
The link pointed to the old OWASP website. Also fixed some typos here and there Resolves: #1136
This commit is contained in:
parent
f2f7f36a6d
commit
ab0433bb67
@ -12,7 +12,7 @@ AcmeObject acme = (AcmeObject)ois.readObject();
|
||||
----
|
||||
|
||||
It is expecting an `AcmeObject` object, but it will execute `readObject()` before the casting ocurs.
|
||||
If an attacker finds the proper class implementing dangerous operations in `readObject()`, he could serialize that object and force the vulnerable application to performe those actions.
|
||||
If an attacker finds the proper class implementing dangerous operations in `readObject()`, he could serialize that object and force the vulnerable application to perform those actions.
|
||||
|
||||
=== Class included in ClassPath
|
||||
|
||||
|
@ -1,13 +1,12 @@
|
||||
|
||||
== Concept
|
||||
In a Server-Side Request Forgery (SSRF) attack, the attacker can abuse functionality on the server to read or update internal resources. The attacker can supply or modify a URL which the code running on the server will read or submit data to. And, by carefully selecting the URLs, the attacker may be able to read server configuration such as AWS metadata, connect to internal services like HTTP enabled databases or perform post requests towards internal services which are not intended to be exposed.
|
||||
In a Server-Side Request Forgery (SSRF) attack, the attacker can abuse functionality on the server to read or update internal resources. The attacker can supply or modify a URL which the code running on the server will read or submit data to. Moreover, by carefully selecting the URLs, the attacker may read server configuration such as AWS metadata, connect to internal services like HTTP enabled databases, or perform post requests towards internal services that are not intended to be exposed.
|
||||
|
||||
== Goals
|
||||
In the exercises on the next pages, you need to examine what the browser sends to the server and how you can adjust the request to get other things from the server.
|
||||
In the exercises on the following pages, you need to examine what the browser sends to the server and adjust the request to get other things from the server.
|
||||
|
||||
== SSRF How-To
|
||||
* https://www.hackerone.com/blog-How-To-Server-Side-Request-Forgery-SSRF
|
||||
|
||||
== A New Era of SSRF by Orange Tsai
|
||||
|
||||
video::D1S-G8rJrEk[youtube, height=480, width=100%]
|
||||
video::D1S-G8rJrEk[youtube, height=480, width=100%]
|
@ -1,11 +1,11 @@
|
||||
|
||||
== Prevent
|
||||
|
||||
To prevent SSRF vulnerabilities in web applications, it is recommended to adhere to the following guidelines:
|
||||
|
||||
* Use a whitelist of allowed domains, resources and protocols from where the web server can fetch resources.
|
||||
* Use a whitelist of allowed domains, resources, and protocols from where the webserver can fetch resources.
|
||||
* Any input accepted from the user should be validated and rejected if it does not match the positive specification expected.
|
||||
* If possible, do not accept user input in functions that control where the web server can fetch resources.
|
||||
* If possible, do not accept user input in functions that control where the webserver can fetch resources.
|
||||
|
||||
== References
|
||||
* https://www.owasp.org/index.php/Server_Side_Request_Forgery
|
||||
* https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html
|
||||
|
||||
|
@ -1,2 +1,2 @@
|
||||
=== Change the request so the server gets information from http://ifconfig.pro
|
||||
=== Change the request, so the server gets information from http://ifconfig.pro
|
||||
Click the button and figure out what happened.
|
||||
|
Loading…
x
Reference in New Issue
Block a user