Re: Java and buffer overflows

[Dave Aitel <dave () immunitysec com>]

Well, here's what I'm saying: The server was written in Java. You send a
long string in the right place, it crashes. The stack is like a billion
calls long, but at the end of it, you get to see 0x4141414141. :>

My assumption was a native code interface, but I could have been wrong.
:>

I didn't bother to write it up because it got taken to the vendor
immediately and fixed. Course, if I'd gone public everyone would have
whined at me for not knowing every single little thing about the bug,
which they were getting owned by already. 

Frankly, half the time going to the vendor isn't worth the effort.
Sometimes, like Mandrake, they just ignore you anyways. 

-dave



On Wed, 2002-06-26 at 23:17, KF wrote:
> So what you are saying is that you found a buffer overflow in some code 
> that uses JNI? As in there was some c based code that the java invoked? 
> I am currious to see how this works.
> -KF
>
>
> Dave Aitel wrote:
>
> > Although, as another poster said, native code invocation is going to
> > continue to be a problem for managed languages such as Java and C# in
> > the years to come. 
> >
> > I've found a buffer overflow in native code invoked by a major
> > application server that happened to be written in Java. It's fixed now,
> > btw. :>
> >
> > -dave

Attachment: signature.asc
Description: This is a digitally signed message part