Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 142390 - CAN-2004-1156 Frame injection vulnerability.
CAN-2004-1156 Frame injection vulnerability.
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: mozilla (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Christopher Aillon
Ben Levenson
: Security
Depends On:
  Show dependency treegraph
Reported: 2004-12-09 09:48 EST by Josh Bressers
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-28 15:11:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:384 high SHIPPED_LIVE Important: Mozilla security update 2005-04-28 00:00:00 EDT

  None (edit)
Description Josh Bressers 2004-12-09 09:48:47 EST
Secunia reported a pair of frame injection vulnerabilities that could
result in popup blocking.


This issue also affects RHEL2.1
Comment 1 Josh Bressers 2004-12-09 09:58:04 EST
This issue also affects galeon, I'm not sure if it would be becuase
galeon uses the mozilla backend, or if it's an issue in the browser
interface.  If a new bug is needed for galeon, please let me know and
I'll file it.
Comment 2 Josh Bressers 2004-12-13 09:36:49 EST
The secunia demo no longer works.  I've created a demo located here
Comment 3 Josh Bressers 2005-04-28 15:11:21 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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