Tag Info

New answers tagged

0

There isn't enough information to go off of here to say whether there is some sort of vulnerability or not. It really depends on what is going on on the server side. From what I can see, my first thoughts on potential vulnerabilities: CSRF - If hash or someOtherValue are actually CSRF tokens then it's probably not vulnerable. Direct Object Reference - If ...


1

When you want one applicaton to prove that it has the right to talk to another (the web service) we are no longer talking about CSRF but about authentication. Usually this is done by secure token sent from web application to web service via a POST request. Check out the first answer to this ...


4

Typically, you do not protect forms that are accessible without authentication. The purpose of a CSRF attack is generally for an attacker to manipulate an authenticated user to perform an action on the site at with the attacker's data and the victim user's authenticated session. Forms that do not require authentication generally aren't vulnerable to being ...


4

Change password forms are commonly bad targets for CSRF attacks as, if they're following good practice, they'll require the users existing password (failure to do so would be a security weakness in and of itself), which someone exploiting a CSRF vuln. is unlikely to know (and if they did, in most cases they would just use that and not bother with CSRF) ...


0

Well its not possible to access the contents of cross domain iframe (by default) using js (that's how the add with be displayed I guess). Otherwise the whole concept of using a pseudo random nonce (particularly those CSRF Mitigation methods that relies on static rewriting of pages) would be a complete failure. Chrome for example shows following error, when ...


0

Answer for the first part: The php version of OWASP CSRF Guard has been implemented as OWASP CSRF Protector (Project name was changed due to diffrenece in design logic). Its available on github for download!


5

You can't currently depend on the Origin header, because it is not implemented in all browsers which are in active use. Apart from that, Origin is not sent in all cases relevant to CSRF, like <img src=http://router/admin.cgi?...>


2

There are CSRF prevention techniques that do not rely upon a session-bound CSRF token, after all there is more than on way to skin a cat. When considering a CSRF protection system, look for any shortcut that doesn't exist with the commonly used CSRF synchronization token pattern. There are three concerns with this proposed CSRF protection system. ...


-1

If the adress ID could be generated from a specified adress (for example, if the adress ID is some binary representation of lat/long of the specified adress that is then Base64-encoded and then converted back and forth via a geolocation service), then you are at same risk of CSRF as originally. But if the ID is random, then you are safe from CSRF. You need ...


1

It looks like it was a private disclosure, so it seems that we will not know this for sure unless someone takes the time to analyze the framework code (or @chrismsnz decides to explain it to us). But from what i could tell, it seems like Session::token() returns a string and Input::get() returns a mixed object. By the rather short explanation they gave, ...


1

This issue was specific in nature, and has since been patched out of Ruby. Flash was more of an example of how one can exploit this issue with a browser plugin, a good example too given it's probably one of the most common plugins, but the actual flaw was in Ruby. We are also talking way edge case that an attacker could pull this off. There is really ...


3

The issue is that the code sample in the OWASP guide is not complete. Specifically, it is missing the implementation of the master_Page_PreLoad method that it wires up in the last line of the Page_Init method. What you would see, if that method were included (and I may go add it shortly here) is that the ViewStateUserKey value being set by the cookie is ...



Top 50 recent answers are included