Enable Plug-ins for Mail & Newsgroups should be off by default

RESOLVED EXPIRED

Status

RESOLVED EXPIRED
15 years ago
10 years ago

People

(Reporter: alex, Assigned: sspitzer)

Tracking

Trunk
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115

I've just got an spam, and watched in amazement as the animated commercial for
some shawing product was downloaded from external web site, and started to play.
 After looking into the source, it appeared that the email was HTML with embeded
shockwave.  Luckily, there was no "IDs" in URLs to identify myself to the
spammer (to confirm my email address, and that I opened the email).

I believe this option should be off by default.  I can hardly imagine any
legitimate email that needs plug-ins.  Allowing an email message to fire off an
arbitrary plug-in automatically is a big security issue.  All virus writer needs
is a bug in popular and wide spread plug-in.

Alternatively, it could be a good idea (if users are allowed to enable plug-ins)
to be able to select which plug-ins are enabled for Mail & Newsgroups, and which
are not (ideally, all should be disabled, and if the user really needs the
functionality (not likely), he/she should be able to be selective).

Reproducible: Always
Steps to Reproduce:
1. Well, I can forward you that spam I got.  Or you could create some HTML
pointing to some external shockwave...
Actual Results:  
Shockwave/Flash plugin was started, files were downloaded from external web site

Expected Results:  
If the default for the setting was off, nothing would happen.
Product: MailNews → Core
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.