Symantec Norton AntiVirus Conflicting MIME Header Vulnerability

BID:4246

Info

Symantec Norton AntiVirus Conflicting MIME Header Vulnerability

Bugtraq ID: 4246
Class: Design Error
CVE:
Remote: Yes
Local: No
Published: Mar 07 2002 12:00AM
Updated: Mar 07 2002 12:00AM
Credit: Reported by Edvice Security Services <[email protected]>.
Vulnerable: Symantec Norton AntiVirus 2002 0
- Microsoft Windows 2000 Professional SP2
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional
- Microsoft Windows 98
- Microsoft Windows ME
- Microsoft Windows NT Workstation 4.0 SP6
- Microsoft Windows NT Workstation 4.0 SP5
- Microsoft Windows NT Workstation 4.0 SP4
- Microsoft Windows NT Workstation 4.0 SP3
- Microsoft Windows NT Workstation 4.0 SP2
- Microsoft Windows NT Workstation 4.0 SP1
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows XP Home
- Microsoft Windows XP Professional
Not Vulnerable:

Exploit / POC

Symantec Norton AntiVirus Conflicting MIME Header Vulnerability

No exploit code required.

Solution / Fix

Symantec Norton AntiVirus Conflicting MIME Header Vulnerability

Solution:
Symantec has offered the following response:

By renaming a file containing malicious code to one with an excluded extension and delivering it in the non-RFC compliant MIME format, Norton AntiVirus' incoming email scan could be bypassed and the malicious file saved on the system as a executable file or as a Microsoft Office document. However, if an attempt is made to execute the malicious file on the computer, the file will be detected by Norton AntiVirus or by the Norton AntiVirus Office plug-in, depending on the file type, which would alert the user to any potential malicious activity. Symantec will have an update to address this RFC issue available via LiveUpdate shortly.

Symantec recommends the following Best Practices to enhance the protection
of your computers from unauthorized access:
1. Keep vendor-supplied patches for all software up-to-date.
2. Be wary of mysterious attachments and executables delivered from email, user groups, and so on.
3. Do not open attachments or executables from unknown sources. Always err on the side of caution.
4. Even if the sender is known, be wary of attachments if the sender does not explain the attachment content in the body of the email. You do not know the source of the attachment.
5. When in doubt, contact the sender before opening the attachment. If still in doubt, delete the attachment without opening it.

© CVE.report 2026

Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.

CVE, CWE, and OVAL are registred trademarks of The MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. This site includes MITRE data granted under the following license.

Free CVE JSON API cve.report/api

CVE.report and Source URL Uptime Status status.cve.report