Closed Bug 468785 Opened 16 years ago Closed 16 years ago

malicious page try to install video codec absolutely mandatory, & loop install?>no>install?

Categories

(Firefox :: Security, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 61098

People

(Reporter: gator, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4

serfing, & popunder... I close them...
it opens new window without controls...
Try to close window by its [X] but active dialog is in loop... 
Malicious page try to "install video codec" absolutely mandatory
(bug-loop, or malicious mistification, fake dialogs, like native install?), 
& loop: install?>no> ~ ... not installed, must be for video blabla>NO>install? etc
I see, that it's not a codec, but horse ) (?)
Cannot use any controls to kill...

And worse, cannot close only that window - task manager do not show windows of FFox personal ID etc - only 1 process, 1 PID...
how can I kill it without kill all?
[X] in each window must be absolutely mandatory/unlockable and kill any open dialogs etc... only ask - yes/no, and kill it... imho... serious sequrity problem, users often like to "install codecs for see it" 
may be, some troyans that I find, use this method?

bad english, sorry!

Reproducible: Always

Steps to Reproduce:
1. just open http://82.192.88.44/hotsex/movie.php?c=main&id=16
2.
3.
Actual Results:  
opens not killable window with codec install dialog loop

Expected Results:  
aaa...
possibilities to kill any windows(or tabs) of FF at my wish at any time, with any dialogs, etc... without any deadlocks, by [X] and only short dialog yes/no/really?
but not all windows/tabs of FF... imho - it's a crash...
The first "window" is no window and if you click "x" you are in a JS alert loop.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.