I managed to make a local copy of that source in order to find out what it was really trying to do...
And as usual , firebug was a great help in making things rather discreet and easy to see...
The code made social engg request targeted to mobile users, offering them "fake-recharge " for life worths time, and in truth it added those guys who clicked into a predecided community, and posted comments on albums(of the victim).
I maintain a fake profile on orkut from which I do all such things , and I tested this one from it. Now it does work but I wonder how did the creator of this bug find out the exact parameters google's orkut webapp requires in order to successfully process the request ?
Its because of internal details like this, that I believe this guy would have worked on it internally at some point in time. And now that orkut is full of
Asynch request /reply has definitely made the web all the more interesting .....
As a part of my grad coursework, I had demonstrated how flash can be used to override the browser's same origin policy (since flash works on flash's policy ,which is set by website owners,its not fixed like the browsers's same origin policy)...
It basically translates to this: If I have ability to upload an swf movie on your trusted domain, your pretty much screwed(if u run it, and you will, cause that is what social engg will make you do) !
:)
Lately I am busy doing this project on particle simulation, its awesome project , in which I basically try to do about a billion particles simulation in real time. So this field is rather unrelated to security as such, although its my second favorite topic "optimization".
Optimization problems are always interesting in a variety of ways, they basically mess with your brain so much that your consumed by searching for possibilities....and then mathematical tools come to your rescue telling you that you have wasted all your time in-vain , searching for a desert rose....
^_^
Till later, see ya!
No comments:
Post a Comment