Which of the following are the limitations for the cross site request forgery (CSRF) attack?

Last Updated on March 19, 2022 by Admin 2

Which of the following are the limitations for the cross site request forgery (CSRF) attack?

  • The attacker must determine the right values for all the form inputs.
  • The attacker must target a site that doesn’t check the referrer header.
  • The target site should have limited lifetime authentication cookies.
  • The target site should authenticate in GET and POST parameters, not only cookies.
Explanation:

Following are the limitations of cross site request forgeries to be successful:
1. The attacker must target either a site that doesn’t check the Referer header (which is common) or a victim with a browser or plugin bug that allows Referer spoofing (which is rare).
2. The attacker must find a form submission at the target site that does something useful to the attacker (e.g., transfers money, or changes the victim’s e-mail address or password).
3. The attacker must determine the right values for all the form inputs: if any of them are required to be secret authentication values or IDs that the attacker can’t guess, the attack will fail.
4. The attacker must lure the victim to a Web page with malicious code while the victim is logged in to the target site. Since, the attacker can’t see what the target Web site sends back to the victim in response to the forged requests, unless he exploits a cross- site scripting or other bug at the target Web site.

Similarly, the attacker can only “click” any links or submit any forms that come up after the initial forged request, if the subsequent links or forms are similarly predictable. (Multiple “clicks” can be simulated by including multiple images on a page, or by using JavaScript to introduce a delay between clicks). from cross site request forgeries (CSRF) by applying the following countermeasures available:
Requiring authentication in GET and POST parameters, not only cookies.
Checking the HTTP Referer header.
Ensuring there’s no crossdomain.xml file granting unintended access to Flash movies.
Limiting the lifetime of authentication cookies.
Requiring a secret, user-specific token in all form submissions prevents CSRF; the attacker’s site can’t put the right token in its submissions.
Individual Web users can do relatively little to prevent cross-site request forgery.
Logging out of sites and avoiding their “remember me” features can mitigate CSRF risk; not displaying external images or not clicking links in “spam” or unreliable e-mails may also help.

0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments