
I'll quote just the contents:
I. Bypassing attachment detection or invalid detection of attachment
type.
1. Encoded filename or boundary in Content-Type/Content-Disposition
2. Multiple filename or boundary fields in Content-Type /
Content-Disposition
3. Exploitation of poisoned NULL byte
4. Exploitation of unsafe fgets() problem
5. MIME part inside MIME part
6. UUENCODE problems
7. Additional space symbol
8. CR without LF
9. Prohibited characters in the filename
10.Skipped file name
11.Endless UUEncoded messages
12.Different filenames for Content-Type and Content-Disposition
13.Case sensitivity of Content-Type and Content-Disposition
II. Bypassing detection of potentially dangerous content
1. Inability to check Unicode (UCT-2) content
2. Inability to check UTF-7 content
3. Inability to check file marked as UTF-7 Content
4. Inability to check content with short Content-Length
III. What should be done?
1. What client software vendor should do.
2. What server software vendors should do.
3. What system administrators should do.
It contains a lot of info of how users as well as software vendors should act against these incidents.

No comments:
Post a Comment