190343 - Browser "Send Page" should sanity check/sanitize or default attachment name

Status: RESOLVED EXPIRED

(MailNews Core :: Composition, defect)

Description

[david brower]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130

If you go to a URL with a nasty long value and do send page, the attachment file
name generated is that of the nasty URL.  There are two problems seen.  (1) it
is awkward for the recipient to save w/o renaming; (2) intermediate mail servers
with virus detection may treat it as insane attachment and delete it.

Example:  send page of

http://foo.bar.com/HTML/iburdtcorcl.jsp?jttst0=1439458_61637%2C61637%2C-1%2C0%2C&ibudnr=25&jtfm0=_0_0_0_-1_f_nv_&ibucr=5OgKRm7l&etfm1=&ibudf=DD-MON-RRRR&kmcp=0QaHKm7l&jfn=ZG52A12159B0836F627EADDD9E4FFF9B7E214450C14E2B8DA3DF27509B8736EAFECB6B25EC2D4FBDF7CAB31C17DD0644A04E

results in an attachment name of 

foo.bar.com-HTML-iburdt01.jsp-foo=bar&jtfm0=_0_0_0_-1_f_nv_&ibucr=np2pk6dY&etfm1=&ibudf=DD-MON-RRRR&kmcp=irWmd6dY&jfn=ZGDF627D49277A897847263DE5DBEC2E0B91FABD7941683B3481A5F9AFB837DA9719E9F7DD23C59AF65CADDB058B9C6C0B49&srID=1253513

which has been seen to provoke virus complaint of:

A (EMail_Flaw_MIME_Tag_Overflow) virus was detected in the file "suspicious long
filename tag" inside of a message bound for your account on 01/22/2003 22:56:45.
 The following action was taken: deleted.







Reproducible: Always

Steps to Reproduce:
1.  Find a site with long encoded URL
2.  Send Page 
Actual Results:  
 Look at the attachment file name that is generated.  Hmm, long, with encodings.




Expected Results:  
It should have restricted the generated name to a 'safe' character
set with a limited length; Or it might default the
name to something innocuous like 'SentPage' rather than using
the URL in the name at all, similar to mail 'save as file' defaulting
to 'message.eml'



1.2.1

Comment 1

[david brower]

PS, I am told by some security people that there are mail clients that blew up
on receiving mime fields > 200 characters, and this is why virus filtering
checks and rejects messages containing such fields.

Comment 2

[R.K.Aa.]

*** Bug 190340 has been marked as a duplicate of this bug. ***

Comment 3

[Daniel B.]

> It should have restricted the generated name to a 'safe' character set 

That's why it's URL-encoded in the first place!

Comment 4

[Gervase Markham [:gerv]]

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/

Comment 5

[Gervase Markham [:gerv]]

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.