September 9, 2005 3:53 AM PDT
Unpatched Firefox flaw may expose users
- Related Stories
-
Bug hunters, software firms in uneasy alliance
September 6, 2005 -
Microsoft investigates another IE flaw report
August 29, 2005 -
IE flaw opens door to infection on sight
August 9, 2005 -
Major Firefox release delayed
July 21, 2005 -
Coding misstep forces new Firefox release
July 18, 2005 -
Windows flaw could spawn DoS attacks
July 15, 2005 -
A safe browser? No longer in the lexicon
July 7, 2005 -
Mozilla puts bounty on bugs
August 2, 2004
The problem lies in the way Firefox handles Web links that are overly long and contain dashes, security researcher Tom Ferris said in an interview via instant messaging late Thursday.
He posted an advisory and a proof of concept to the Full Disclosure security mailing list and to his Security Protocols Web site.
The security vulnerability is a buffer overflow flaw that "allows for an attacker to remotely execute arbitrary code" on a vulnerable PC, Ferris said. An attacker could host a Web site containing the malicious code to exploit the flaw, he said. Though his proof of concept only crashes Firefox, Ferris claims he has been able to tweak it to run code.
Buffer overflows are a commonly exploited security problem. They occur when a program allows data to be written beyond the allocated end of a buffer in memory. A computer can be made to execute potentially malicious code by feeding in extra data that is designed to flood the buffer.
Ferris reported the bug to the Mozilla Foundation on Sunday, intending to go through the organization's bug-reporting process, he said. However, in an example of the uneasy alliance between security researchers and software makers, he decided to publicly disclose the flaw after a run-in with Mozilla staff, he said.
Mozilla, which coordinates the development of Firefox and distributes the software, on Friday confirmed the bug but said the scope of the flaw is still under investigation. The organization said it received the bug report on Tuesday, not Sunday.
"We believe there is a buffer overflow issue," said Mike Schroepfer, director of engineering at Mozilla. "We are still determining whether it is exploitable in an attack."
Users are currently not at risk because there are no known attacks that take advantage of the flaw, Schroepfer said. Mozilla is working on a fix that will be released with an upcoming version of Firefox, he said.
Mozilla is unhappy with the disclosure of the flaw. "We'd like to make sure that by the time something goes public, we have a solution for the users," Schroepfer said.
Since the debut of Firefox 1.0 in November, usage of the open-source browser has grown. Security has been a main selling point for Firefox over Microsoft's Internet Explorer, which has begun to see its market share dip slightly--for the first time in years.
However, Firefox has had its own security woes. Several serious holes in the browser have been plugged since its official release, and experts have said that safe Web browsers don't exist.
The public bug disclosure comes just as Mozilla released the first beta of Firefox 1.5. The final release of the next Firefox update, which includes security enhancements, is due by year's end, according to the Firefox road map.
Ferris has found bugs in Microsoft software before, including a yet-unpatched flaw in Internet Explorer that Microsoft still has under investigation.
Earlier this month Microsoft credited Ferris with reporting a bug in a Windows feature called Remote Desktop Protocol that could allow an attacker to remotely restart Windows systems.
48 comments
Join the conversation! Add your comment
<a class="jive-link-external" href="http://www.security-protocols.com/firefox-death.html" target="_newWindow">http://www.security-protocols.com/firefox-death.html</a>
<html>
<A HREF="#">crash</a>
</html>
when i click on the crash link, it directs me to the google "web" search page. the address bar is: "keyword:---------------------------------------------" and the google text field (where you enter your search terms) is: "---------------------------------------------". below that is: "The 'I'm Feeling LuckyTM' button automatically takes you to the first web page returned for your query.
An 'I'm Feeling Lucky' search means less time searching for web pages and more time looking at them."
no crashes. did i do something wrong in creating the html file?
<a class="jive-link-external" href="http://www.security-protocols.com/firefox-death.html" target="_newWindow">http://www.security-protocols.com/firefox-death.html</a>
<html>
<A HREF="#">crash</a>
</html>
when i click on the crash link, it directs me to the google "web" search page. the address bar is: "keyword:---------------------------------------------" and the google text field (where you enter your search terms) is: "---------------------------------------------". below that is: "The 'I'm Feeling LuckyTM' button automatically takes you to the first web page returned for your query.
An 'I'm Feeling Lucky' search means less time searching for web pages and more time looking at them."
no crashes. did i do something wrong in creating the html file?
man i'm dumb...
man i'm dumb...
One of the great things about open source software is if you don't like something you can change it.
In short, if you want something done right (at least according to your point of view) do it yourself. Mozilla's website has tutorials on XUL and the Javascript.
One of the great things about open source software is if you don't like something you can change it.
In short, if you want something done right (at least according to your point of view) do it yourself. Mozilla's website has tutorials on XUL and the Javascript.
It crashed so fast that it made me laugh
It crashed so fast that it made me laugh
- <a class="jive-link-external" href="https://addons.mozilla.org/messages/307259.html" target="_newWindow">https://addons.mozilla.org/messages/307259.html</a>
"On September 9, the Mozilla team released a configuration change which, as a temporary measure to work around this problem, disables IDN in the browser..."
- <a class="jive-link-external" href="https://addons.mozilla.org/messages/307259.html" target="_newWindow">https://addons.mozilla.org/messages/307259.html</a>
"On September 9, the Mozilla team released a configuration change which, as a temporary measure to work around this problem, disables IDN in the browser..."