Firefox 0.9.2, Thunderbird 0.7.2, Mozilla 1.7.1 Coming Soon

Thursday July 8th, 2004

Branches have been created for three of's latest releases, in order to fix an external Windows protocol handler bug. The fix involves disabling the shell: protocol handler, which was found to enable pages to run executables on Windows via a link. Builds should officially be available shortly, and there will also be an XPI offered to disable the pref. Alternatively, you can set the pref in about:config to false to remove the exploit. (This will only set it on your current profile, if you have more than one profile, or could be creating more, you should use the XPI or the updated build.)

More information about the exploit can be found in this post on the FullDisclosure mailing list.

Update: The XPI to disable the pref is now available.

Another Update: has published a document on the issue.

Yet Another Update: There is an eWeek article about the exploit as well as a discussion at Slashdot. The now public bug report that covers the shell: vulnerability is bug 250180 (no unnecessary comments please). Some may find it notable that a patch was issued less than forty-eight hours after this bug was filed.

Yet Another Update: If you are not using Windows, you are not at risk from this bug. If you are using Windows, go to to see if you are vulnerable.

#4 Two Bugs!

by schapel

Thursday July 8th, 2004 11:52 AM

You are replying to this message

I discovered two bugs while trying to set the preference mentioned.

1) When I typed "shell" into the Filter textbox and discovered that the pref did not yet exist, I tried to right-click to get a context menu so I could add the new pref. No context menu appeared! I later figured out that you need to actually right-click on an existing pref to add a new (unrelated) pref. This is bug 238955 <<>>.

2) When I added the new pref, I was using the filter "network.p". After adding the pref, it did not appear in the filtered list as it should have. I had to re-filter the list to get the new pref to show up. Can someone find the bug number for this?