Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Browser holes in Firefox and IE

  • Please log in to reply
No replies to this topic

#1 Enthusiast


  • Members
  • 5,898 posts
  • Location:Florida, USA
  • Local time:07:20 AM

Posted 10 June 2005 - 11:39 AM

Browser hole affects Firefox 1.0.3 and 1.0.4

Secunia reports a frame-injection vulnerability in Firefox 1.0.3 and
1.0.4. Mozillazine has details, including a comment that you can
close the hole (until 1.0.5 is released) by clicking Tools, Options,
Advanced, Tabbed Browsing and changing "open links in a new window"
to "open links in a new tab in the most recent window":

A Secunia bulletin also notes that a similar hole has existed in
Internet Explorer 5.x and 6.x since June 2004 and has not yet been
patched by Microsoft (but there is a workaround):

4. XP Service Pack 2 causes "Page cannot be displayed" errors

Microsoft reported on June 7 that XP SP2 causes an unexpected error
when you click the Back button in Internet Explorer to go to a page
on which you previously submitted form data. A hotfix is available
and there's also a workaround as an alternative:

5. Windows XP SP2 and 2003 SP1 cause errors browsing Web sites

Microsoft says installing XP Service Pack 2 or Windows Server 2003
Service Pack 1 causes error messages when browsing or editing local
Web sites hosted on IIS 5.1 or 6. This also affects ASP.NET projects
in MS Visual Studio 2003. There are two possible workarounds:

The above is from a newsletter I got from Windows Secrets.

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users