** HEAD'S UP ** FireFox Java Vulnerability

Greeting's

A new vulnerability has been discovered in Mozilla FireFox V 1.x which can be used remotely to gain access to potentianlly sensitive information.

Original Advisory : https://bugzilla.mozilla.org/show_bug.cgi?id=288688

Other reference advisory : http://secunia.com/advisories/14820/

A proof of concept is found here : http://secunia.com/mozilla_products_...exposure_test/

Above link can be used to test if your system is vulnerable to the exploit. Each time you click on the link 10 Kb of memory will read from your system. BUT NOTE I TRIED IT MORE THEN 6 TIMES AND MY BROWSER CRASHED.

Currently no patch is released but this vulnerability can be fixed by DISABLING JAVA SUPPORT.


Other Reference : http://cubic.xfo.org.ru/index.cgi?read=53004

This exploit is classified as : "Moderately critical".

Blast - That's got me!

Thanx for the heads up

Steve

Interesting. Anyone got IE that could try it? It was effective against Mozilla but I'm curious if this is more a JRE issue than a browser issue.

Greeting's

I tried the test with IE (fully updated) but it only show's "xxxxxxxxx......." and almost endless xxxx..

Anyway I just want to know for all those useres who tried the proof of concept code did you your firefox crash and if yes after how many tries ? Mine crashes after reading 60 Kb of memory.

I got up to 41 on my Firefox 1.0.1. My mozilla crashed the 1st time after 6 and then went endless on the 2nd try. Both of these are on Linux (RH9)

I dont know if I've even installed any java plugins for FF but I'll still disable it when I get home.

I tip my hat to you sir. (or madame)

Greeting's

I am not sure what is the latest version of firefox on linux but on windows it is 1.0.2. And MsMittens same here i got up 30 in the second try.

Byte: it's the same on Linux, I've just been lazy about updating my abuse machine (it's a machine I use in wargames classroom). ;)

Quote:

---

Originally posted here by ByTeWrangler
Currently no patch is released but this vulnerability can be fixed by DISABLING JAVA SUPPORT.

---

NO. The bug is in the JavaScript engine. Disabling Java has absolutely no effect (with regards to this bug). You should disable JavaScript support. Java and JavaScript are NOT the same thing...

Quote:

---

Source - http://secunia.com/advisories/14820/
The vulnerability is caused due to an error in the JavaScript engine, as a "lambda" replace exposes arbitrary amounts of heap memory after the end of a JavaScript string.

---

Good call!

Thanks for the info.

Yo!