Firefox 3 Vulnerability Reported
By Ashish MohtaFSecure via Tipping point had reported a zero day vulnerability in latest version of Firefox 3 and earlier versions of Firefox are also affected. The technical details of the vulnerability and how it works has not been disclosed until the patch is made availble. They have reported this issue to the Security team of Mozilla.
Successful exploitation of the vulnerability could allow an attacker to execute arbitrary code. Not unlike most browser based vulnerabilities that we see these days, user interaction is required such as clicking on a link in email or visiting a malicious web page.
TippingPoint hasn’t revealed any technical details of the vulnerability. They will not do so until a patch is available. The vulnerability requires some user interaction such as clicking on an e-mail link or visiting a malicious page.
So all you can do is :
- Make sure you are browsing safe and not moving to every other crap site in internet.
- Secondly keep your Firefox Update Button on. So as soon as the patch is released you are prompted for it.
|
|
  (+10 rating, 2 votes) Loading ... |
 |
About The Author of this article: Ashish is one of the co-author of this blog and writes on various interesting softwares, PC tips and more. You can read more of his articles here. |
Enjoyed this article? Download our Toolbar ( for Free ) and read us more quickly or Free Subscribe to the Full RSS Feed or Get Post like this in your Inbox Free Subscribe via Email
Thanks for this update
I’m honestly surprised somebody hasn’t already started spewing s* from their a* about how Firefox 3 already has a vulnerability…
Considering that it was probably discovered on Firefox 2, and that it was then later tested on 3, where it was found to still exist…
It hardly seems worth it, saying that the first vulnerability was found, in a case like that.
And no, to preempt any accusers, I don’t hold a double-standard. I say the exact same thing when I hear about vulnerabilities in IE and other browsers, as well.
If the browser was only released a few days prior, even a week or two, and the vulnerability exists in previous versions, it really isn’t all that surprising that it exists in the current version. I wouldn’t be surprised if a slew of vulnerabilities were suddenly “found” by crackers and malcontents who were holding on to a bunch of them, just to piss on .