CSRF
This is a good start - https://www.hackthis.co.uk/articles/cross-site-request-forgery
I don’t have any specific examples, but once you know the theory of it you can start to look how sites prevent it, e.g. HackThis
Folding@Home Stats | Official Thread | Team Number: 223679
w3af have a plugin for detection of CSRF.
Folding@Home Stats | Official Thread | Team Number: 223679
@Zoino: I don’t really get what you mean. As far as I know about CSRF, the attacker uses cookies as his “key” to transmit his malicious request(s). He just doesn’t care about the quantity of cookies, as long as they are still there.
11 years ago | edited 11 years ago
0
CSRF: https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)
The attacker forces the end user to execute unwanted actions. Reference above.
Additional sites:
http://en.wikipedia.org/wiki/Cross-site_request_forgery
https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)_Prevention_Cheat_Sheet#Double_Submit_Cookies
As previously stated, the attacker doesn’t care about the quantity. Quality beats quantity. :)
11 years ago | edited 11 years ago
0
From the research I done, I guess an attacker may use POST or GET methods to retrieve a cookie. Sorry for all the links. :P
http://www.php.net/manual/en/reserved.variables.request.php
http://www.php.net/manual/en/language.variables.external.php
Perhaps you’ll find these sources useful.
11 years ago
0
Ok, good luck.
@Zoino: The cookie is not the final target. Say, you want to poison an enemy general (send malicious request), you have his assistant poisoning him (use authenticated cookie to send that request). There’s no need to care about that assistant.
[quote=Zoino]No i mean if a site stores say 10 cookies, and only one of them stores the cookie for the username and password. How would you target just that cookie?[/quote]
@Zoino: From a developer’s perspective or from an attacker’s perspective?
As a developer, you can print all the cookies (PHP):
print_r($_COOKIE);
Or just read the value of a cookie:
echo $_COOKIE['cookie_name'];
But you can’t read a cookie from another domain (because of security problems, of course). :p