DO NOT DEAL WITH THIS MEMBER
http://kuza55.blogspot.com/2008/02/explo...d-xss.html
Using something like this may still work depending on how the session cookies work on minecrafts site.
(Jun 13, 2015 03:20 PM)ThePenumbra Wrote: Sorry Haxxy baby, but are you dumb o.o?
I can make a link which on click auto-submits a POST request.
OP, got skype/xmpp?
If yes, PM me it. No, that won't work at all. Rifk
af
Jun 15, 2015 02:08 AM
(This post was last modified: Jun 15, 2015 02:16 AM by Gee4rce.)
(Jun 13, 2015 03:20 PM)ThePenumbra Wrote: I can make a link which on click auto-submits a POST request.
This is true, but if the website i.e. has no other vulnerability (which you may could use in combination to auto-launch the XSS),
AND further is even CSRF protected, then there is no real chance for a propper exploitation.
(Jun 13, 2015 03:20 PM)ThePenumbra Wrote: Sorry Haxxy baby, but are you dumb o.o?
You not call HaxOr dumb mate... 😅 If he says something, then it has a reason.
(Jun 13, 2015 11:45 PM)Ɲorman Bates Wrote: No one done anything with it yet? Waiting for a big hax0r to get something done
So why not do something by your own?
Greets, Gee.
(Jun 14, 2015 07:01 PM)Im gone brah Wrote: No, that won't work at all. Rifk
Why not?
(Jun 15, 2015 02:08 AM)Gee4rce Wrote: This is true, but if the website i.e. has no other vulnerability (which you may could use in combination to auto-launch the XSS),
AND further is even CSRF protected, then there is no real chance for a propper exploitation.
Why do you need another vulnerability?
If you have a proper POST XSS without csrf protection in it, you can just upload html with js on another site. You dont need to get the response, you just need to make the request.
Jun 15, 2015 04:03 AM
(This post was last modified: Jun 15, 2015 04:05 AM by Gee4rce.)
(Jun 15, 2015 03:55 AM)ThePenumbra Wrote: Why do you need another vulnerability?
As for this one, there was a CSRF protection.
So as long as you not find another vulnerability, this XSS alone is not pretty much to exploit something interesting from it.
(Jun 15, 2015 03:55 AM)ThePenumbra Wrote: You dont need to get the response, you just need to make the request.
You must be new here, calling HaxOr dumb and explaining me how XSS works 😅
(it's ok though, no problem ;)
Greets, Gee.
(Jun 15, 2015 04:03 AM)Gee4rce Wrote: As for this one, there was a CSRF protection.
So as long as you not find another vulnerability, this XSS alone is not pretty much to exploit something interesting from it.
You must be new here, calling HaxOr dumb and explaining me how XSS works 😅
(it's ok though, no problem ;)
Greets, Gee.
If you take a look at my previous post in this thread, I said I didnt notice the CSRF protection.
Jun 15, 2015 04:30 AM
(This post was last modified: Jun 15, 2015 04:36 AM by Gee4rce.)
Yes, sure,
but if you also take a look at your pre-previous post, you stated "Why do you need another vulnerability?", so i just explained why i put this statement before.
But np, lets move on here and get back to the topic guys...
Greets, Gee.
Jun 15, 2015 07:10 AM
(This post was last modified: Jun 15, 2015 07:19 AM by Im gone brah.)
ThePenumbra Wrote:Why not?
Are you for real, last time I checked this is not possible due to CSRF protection mechanism. Prove me wrong and I'd be happy to change my opinion. I'd also like to state that this XSS vulnerability is pretty much limited and really useless. Edit: If you want feel proudly with piping alerts, I won't stop you.
af
You realise you can just use the XSS to extract the token using javascript right? Why are people crying over the token being some kind of ultimate protection?
It's 2015 now, step it up guys.
Jun 15, 2015 10:09 AM
(This post was last modified: Jun 15, 2015 10:11 AM by Gee4rce.)
(Jun 15, 2015 10:03 AM)LevelUp Wrote: You realise you can just use the XSS to extract the token using javascript right? Why are people crying over the token being some kind of ultimate protection?
It's 2015 now, step it up guys.
Nice to see you back LevelUp!!
But looks like you was sleeping while writing your answer 😅 ->
how would you extract the session or CSRF token, if the CSRF token already prevents an attacker from launching the XSS 'remotely' ? ...(as that would be required to extract anything Session related)
Greets, Gee.
Jun 15, 2015 10:16 AM
(This post was last modified: Jun 15, 2015 10:18 AM by LevelUp.)
(Jun 15, 2015 10:09 AM)Gee4rce Wrote: Nice to see you back LevelUp!!
But looks like you was sleeping while writing your answer 😅 ->
how would you extract the session or CSRF token, if the CSRF token already prevents an attacker from launching the XSS 'remotely' ? ...(as that would be required to extract anything Session related)
Greets, Gee.
To leave you wanting more I suggest you look into the Sammy Worm which used javascript to bypass myspace anti-csrf, but I wasn't sleeping.
Quick edit: Because I don't think any of you will actually bother looking into that you can just go on Owasp and it will set you straight.
(Jun 15, 2015 10:39 AM)Yani Wrote: He was able to bypass CSRF because he got a persistent XSS that was running on the MySpace domain
^ Thats what i tried to explain LevelUp, OP's scenario is just a reflected POST XSS, thus it will not work extracting stuff.
(Jun 15, 2015 10:16 AM)LevelUp Wrote: To leave you wanting more I suggest you look into the Sammy Worm which used javascript to bypass myspace anti-csrf, but I wasn't sleeping.
Quick edit: Because I don't think any of you will actually bother looking into that you can just go on Owasp and it will set you straight.
Leaving this here in the hopes LevelUp sees it. I can't PM you at the moment, gimme a buzz when you're round.
|