Discussion of bugs in Mozilla Firefox
<a href="http://secunia.com/advisories/16764/">SA16764 - Firefox URL Domain Name Buffer Overflow</a> was just reported today by Secunia and is rated highly critical.
(For) Now Fx is rated as vulrnerable as IE.
Tom Ferris has discovered a vulnerability in Firefox, which can be exploited by malicious people to cause a DoS (Denial of Service) or potentially to compromise a user's system.
The vulnerability is caused due to an error in the handling of an URL that contains the 0xAD character in its domain name. This can be exploited to cause a heap-based buffer overflow.
Successful exploitation crashes Firefox and may potentially allow code execution but requires that the user is tricked into visiting a malicious web site or open a specially crafted HTML file.
The vulnerability has been confirmed in version 1.0.6, and is reported to affect versions prior to 1.0.6, and version 1.5 Beta 1.
Temporary workaround: Disable IDN support (toggle <strong>network.enableIDN</strong> in <a href="http://www.mozillazine.org/misc/about:config/">about:config</a>).
1.5beta1 looks safe (doesn't crash)
Did Secunia report this bug to Mozilla first? If not, how nice of them to publish the bug without giving the Firefox developers the chance to fix it (standard practice when they discover bugs in IE, for example).
If you follow the Originally Reported link, http://security-protocols.com/advisory/ ... visory.txt
you will see in there:
Mozilla was notified, and im guessing they are working on a patch. Who knows though?
So, in other words, they notified Mozilla, but then didn't wait for a patch to be issued. I've noticed that Secunia frequently witholds information about bugs in IE until Microsoft has a "patch day" and makes fixes available. So, I guess I'm wondering what happened here.
Okay, I've done this. But what is it I've disabled and what am I giving up by doing so?
Win10 (64bit): FF 105.0.1 (64bit), TB 102.3.0 (32-bit) ║ Android 10 & 12: FF Mobile 104.2.0, No TB for Android available, dammit!
What a fool believes he sees, no wise man has the power to reason away - Doobie Brothers
I don't think that there is any favoritism going on with Secunia. This particular vulnerability was posted on http://security-protocols.com on Sept 5th so, it was public knowledge. I think the situations that you speak of with Secunia not posting an advisory until after the patch are different because those vulns were not publicly known.
Thanks Unarmed. I have notified Secunia of this workaround. Hopefully they will add it to the Solution section of the advisory.
Can't find anything in Bugzilla.
There probably is one that has the security flag set and is not accessable to mere peons like us
I will open one anyways just to be sure.
...and there is a bug for it already.
http://www.betanews.com/article/Securit ... 1126279570
whats that all about?
Who is online
Users browsing this forum: No registered users and 0 guests