Bug 188783 - CVE-2006-1740 Secure-site spoof (requires security warning dialog)
Summary: CVE-2006-1740 Secure-site spoof (requires security warning dialog)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mozilla
Version: 5
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Christopher Aillon
QA Contact: Ben Levenson
URL:
Whiteboard: reported=20060412,source=mozilla,emba...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-13 02:18 UTC by Josh Bressers
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Fixed In Version: FEDORA-2006-487
Clone Of:
Environment:
Last Closed: 2006-06-24 15:42:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Josh Bressers 2006-04-13 02:18:47 UTC
Secure-site spoof (requires security warning dialog)


Tristor reports that it was possible to spoof the browser's secure-site
indicators (the lock icon, the site name in the URL field, the gold URL
field background in Firefox) by first loading the target secure site in a
pop-up window, then changing its location to a different site.

If the user has turned on the "Entering secure site" modal warning dialog
then the window location can be changed while that dialog is displayed and
the secure-browsing indicators from the original site will remain.

These dialogs are turned off by default in Firefox, and most Suite users
click the checkbox to turn them off.

Workaround

Turn  off the "Entering encrypted site" warning dialog if you have not
already.

References

[1]https://bugzilla.mozilla.org/show_bug.cgi?id=271194


This issue also affects FC4

Comment 1 Josh Bressers 2006-04-24 12:30:03 UTC
Lifting embargo

Comment 2 David Eisenstein 2006-06-24 15:42:59 UTC
This bug was fixed for FC4 in Fedora Update FEDORA-2006-488
<http://www.redhat.com/archives/fedora-package-announce/2006-May/msg00019.html>.

This bug was fixed for FC5 in Fedora Update FEDORA-2006-487
<http://www.redhat.com/archives/fedora-package-announce/2006-May/msg00018.html>.


Note You need to log in before you can comment on or make changes to this bug.