i've haerd some XSS bug which was fixed real quick by facebook guyz, it was the same bug found in orkut it was something as follows:
inserting malicious javascript into the "captions" of your pitcure
|
Security Expert
|
|
| 20Apr2009,23:25 | #11 |
|
Ambitious contributor
|
![]() |
| 21Apr2009,00:10 | #12 |
|
Quote:
Originally Posted by SpOonWiZaRd The aim isn't to inject executable code into the program. It's to overwrite a pointer/return address on the runtime stack so that it points to the memory address where your instructions are stored, so when the program pops its last method/function off the stack, it returns to your instructions and executes them instead of returning to where the method was called from. Most buffer overflows are used for local privilege escalation, but every now and then they can be exploited remotely on web applications (like what you're talking about) or other connected programs (like p2p clients or internet browsers). They mostly work on programs that were coded in c/c++. You don't try them on servers themselves. You look for them in applications/OS's the servers are running. Finding a site that uses a web application that is vulnerable to buffer overflow is pretty rare, so if you meant hack facebook by buffer overflow on a web application, you can pretty much forget about it. They'll have all their applications updated. If you meant root their server with a buffer overflow, that's more possible, but incredibly stupid to try without taking many precautions first, and not worth the trouble just to see who viewed your profile. The best way to hack a social networking site is by using xss/js injections in vectors they haven't thought to filter or social engineer/keylog an admin. @indiansword, I remember hearing about that. If I'm correct, it was not even a matter of days before it was fixed, but several hundred thousand accounts were still compromised because of it. I wonder how long it would have gone undetected if whoever found it hadn't made it so obvious. |
|
Security Expert
|
|
| 21Apr2009,01:05 | #13 |
|
the person who found i think was probably new to XSS so experienced users understood it so quickly.
The founder directly put the script to steal the cookies, instead of that he should have injected an IFRAME and hide the script and steal the cookies with it. If he'd have done as i said then he'd have got chance to hack many more accounts and facebook people wouldnt even come to know about it. |
|
Know what you can do.
|
![]() |
| 21Apr2009,11:39 | #14 |
|
i read at this link http://en.wikipedia.org/wiki/Stack_buffer_overflow that its possible to inject executable code with stack buffer overflow... I also heard about that XSS thing and I think it was possible to use greasemonkey in mozilla.
|
|
Ambitious contributor
|
![]() |
| 21Apr2009,15:35 | #15 |
|
Quote:
Originally Posted by SpOonWiZaRd |
|
Know what you can do.
|
![]() |
| 22Apr2009,00:08 | #16 |
|
Quote:
Originally Posted by fourthdimension now I see that as injecting executable code, maybe I have it wrong... Help me on the right path as to what that means please. Don't get me wrong as I came to this site for the purpose of learning. |
|
Security Expert
|
|
| 22Apr2009,00:33 | #17 |
|
I think as far as facebook is concerned there is one more vulnerability in while adding some user as a friend to inject XSS into it. I am not really sure but i think there is some. I m in office so cant open facebook right now.
|
|
Ambitious contributor
|
![]() |
| 22Apr2009,01:30 | #18 |
|
Quote:
Originally Posted by SpOonWiZaRd |
|
Know what you can do.
|
![]() |
| 23Apr2009,10:47 | #19 |
|
I found something new just now, you can read about it at http://infosecurity.us/?p=4928 don't know if the vulnerability has been fixed....
|
|
Ambitious contributor
|
![]() |
| 23Apr2009,11:13 | #20 |
|
Nice find. December of 08? Not valid anymore. Facebook usually fixes holes within a few days of their discovery.
|


The aim isn't to inject executable code into the program. It's to overwrite a pointer/return address on the runtime stack so that it points to the memory address where your instructions are stored, so when the program pops its last method/function off the stack, it returns to your instructions and executes them instead of returning to where the method was called from. 