Cross Site Request Forgery

Cross Site Request Forgery ( CSRF ) is a type of website exploit carried out by issuing unauthorized commands from a trusted website user.  CSRF exploits a website’s trust for a particular user's browser, as opposed to cross-site scripting, which exploits the user’s trust for a website.

A CSRF usually uses a browser's "GET" command as the exploit point. CSR forgers use HTML tags such as "IMG" to inject commands into a specific website. A particular user of that website is then used as a host and an unwitting accomplice. Often the website does not know that it is under attack, since a legitimate user is sending the commands. The attacker might issue a request to transfer funds to another account.
e.g
amanvera send some html having below img. unforunately at that time both user (poonm & amanvera) are login to their bank(i.e yourbank). whenever poonam execute the html code send by amanverma. following img src will execute self, and tranfer money from poonam to amanverma account.
<img src="http://www.yourbank.com/transfer?from=poonam&to=amanverma&amount=1000000">


A CSRF attack is hard to execute because a number of things have to happen in order for it to succeed:

• The attacker must target either a website that does not check the referrer header (HTTP_REFERER) or a user/victim with a browser or plug-in bug that allows referrer spoofing (which is rare).
• The attacker must locate a form submission at the target website, which must be capable of something like changing the victim's email address login credentials or doing money transfers.
• The attacker must determine the correct values for all of the form's or URL's inputs. If any of them are required to be secret values or IDs that the attacker cannot accurately guess, the attack will fail.
• The attacker must lure the user/victim to a Web page with malicious code while the victim is logged in to the target site.

For example, suppose that Person A is browsing his bank account while also in a chat room. There is an attacker (Person B) in the chat room who learns that Person A is also logged in to bank.com. Person B lures Person A to click on a link for a funny image. The "IMG" tag contains values for bank.com’s form inputs, which will effectively transfer a certain amount from Person A’s account into Person B’s account. If bank.com does not have secondary authentication for Person A before the funds are transferred, the attack will be successful.

Best Related Posts are Following:

1. How can I prevent SQL-injection in PHP?.
2. What is Best method for sanitizing user input with PHP?.
3. Difference between Notice and warning and fatal error.
4. How can I prevent SQL-injection in PHP [SOLVED].
5. PHP Register Globals.
6. PHP Sessions and Cookie and Security.
7. Free Boost Web Application By 20% in Simple Steps.
8. PHP Check Mime Type of File - Return Information About A File.
9. Crontab Interview Questions and Answers.
10. Improve Ajax Performance.
11. PHP Captcha Code Example Code Snippets.
12. PHP - Secure Ajax Call from Hackers - Example.
13. htaccess code snippets example.
14. Manage Cron Job with PHP - SSH2 Connection.
15. Shared Server Security Risk open_basedir disable_functions disable_classes.
16. Spoofed Forms - Stop Spoofed Form Submissions.
17. Session Fixation.
18. Session Hijacking.
19. openssl private encrypt.
20. Cross Site Request Forgery.
21. SQL Injection Attack - PHP & MySQL.
22. Cross-Site Scripting - cross site scripting examples.
23. PHP INI settings.