Closed
Bug 309267
Opened 19 years ago
Closed 13 years ago
Consider using a whitelist of allowed JavaScript properties and methods for mailnews
Categories
(MailNews Core :: Security, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jruderman, Unassigned)
References
Details
The blacklist of properties and methods for mail messages is large and hard to get right. See most of bug 84545's dependencies for things that were omitted at one time or another. What kinds of things do scripts in mail do, and what properties and methods do they usually use? What would a whitelist have to look like to allow, say, 90% of legitimate JavaScript-containing messages work?
Comment 1•19 years ago
|
||
> The blacklist...is large and hard to get right. Isn't this why we (and Microsoft) simply turned off Javascript in mail? > legitimate JavaScript-containing messages What does one of those do? How do you allow any "legitimate" javascript while preventing at the very least a mail-based DOS? With Javascript turned on even if all "wiretap" and "DOS" holes are closed (magically) mail could still be an avenue for most of the exploits the browser has had. In the browser the user has to stumble across the bad guys (and that's easy enough); the sad history of the anti-spam fight shows there's no way to stop the bad guys from coming to you in mail.
Updated•16 years ago
|
QA Contact: security
| Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•