Newsletters

Select newsletters below and click the button to sign up!

Boston News NY News
DC News Internet Daily
SiliconValley News
InternetNews Business Report




Become a Marketplace Partner



Partner With Us















Internetnews Bloggers

Recent Entries

Archives

April 2009
Sun Mon Tue Wed Thu Fri Sat
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30    

Monthly Archives

Search The Blog

Netstat -vat by Sean Michael Kerner (bio)

A command line view of IT



Firefox 3 at low/high risk from new flaw

sr-firefox3.jpg
From the "tomato, tom-ah-to" files:

Mozilla Firefox 3 is at risk from a new flaw that is currently unpatched. Whether the flaw is high or low risk depends on who you ask (or read).

This AM Radware issued a press release calling the vulnerability - critical. I contacted Mozilla and a few hours later they had an advisory up on their site calling the vulnerability - low risk.

Mozilla explains the vulnerability to be:
A null pointer dereference in the content layout component of Firefox allows an attacker to crash the browser when a user navigates to a malicious page.
As a mitigating factor, Firefox's session restore will allow a user to restart their browser and be taken back to where they left off. The vulnerability requires that a user visits a malicious site with the malicious code on it, but as far as I can tell it does not require any further user interaction.

In my book, any flaw that does not require user interaction is significant.

True the impact is limited, and Mozilla notes that the issue is under investigation. But I hope that we see an incremental patch for this issue before I see a module for it up on Metasploit.

| Comments (1) | TrackBacks (0) | Share

0 TrackBacks

Listed below are links to blogs that reference this entry: Firefox 3 at low/high risk from new flaw.

TrackBack URL for this entry: https://swarm.jupitermedia.com/mt-tb.cgi/4161

1 Comments

James said:

It's basically a way to get the browser to crash - not a big find. I've seen the crash reporter a few times using FF3. Doesn't mean it's a security issue unless it's an exploitable crash - I'm kinda surprised a security company didn't bother to look to see if it is a security issue before trumpeting it in a press release.

Leave a comment