var-200411-0163
Vulnerability from variot
Symantec Norton AntiVirus 2004, and earlier versions, allows a virus or other malicious code to avoid detection or cause a denial of service (application crash) using a filename containing an MS-DOS device name. Norton AntiVirus is affected by a scan evasion vulnerability when handling files with MS-DOS reserve device names. This issue is due to a design error that allows the files to avoid being scanned. It should be noted that this vulnerability only arises once the file is already present on a vulnerable computer. All Norton AntiVirus products are able to detect malicious files through incoming email. BACKGROUND
Symantec's Norton AntiVirus protects email, instant messages, and other files by automatically removing viruses, worms, and Trojan horses. More information about the product is available from http://www.symantec.com
II.
The problem specifically exists in attempts to scan files and directories named as reserved MS-DOS devices. Reserved MS-DOS device names are a hold over from the original days of Microsoft DOS. The reserved MS-DOS device names represent devices such as the first printer port (LPT1) and the first serial communication port (COM1). Sample reserved MS-DOS device names include AUX, CON, PRN, COM1 and LPT1. reserved device names can be creating with standard Windows utilities by specifying the full Universal Naming Convention (UNC) path. The following command will successfully copy a file to the reserved device name 'aux' on the C:\ drive:
copy source \\.\C:\aux
III. ANALYSIS
Exploitation allows attackers to evade detection of malicious code. Attackers can unpack or decode an otherwise detected malicious payload in a stealth manner.
IV. DETECTION
iDEFENSE has confirmed the existence of this vulnerability in the latest version of Norton AntiVirus. It is reported that earlier versions crash upon parsing files or directories using reserved MS-DOS device names.
V. WORKAROUND
Ensure that no local files or directories using reserved MS-DOS device names exist. On most modern Windows systems there should be no reserved MS-DOS device names present. While the Windows search utility can be used to locate offending files and directories, either a seperate tool or the specification of Universal Naming Convention (UNC) must be used to remote them. The following command will successfully remove a file stored on the C:\ drive named 'aux':
del \\.\C:\aux
VI. VENDOR RESPONSE
"Symantec engineers have developed a fix for this issue for Symantec Norton AntiVirus 2004 that is currently available through LiveUpdate. The fix is being incorporated into all other supported Symantec Norton AntiVirus versions and will be available through LiveUpdate when fully tested and released."
More information is available in Symantec Security Advisory SYM04-015.
VII. CVE INFORMATION
The Common Vulnerabilities and Exposures (CVE) project has assigned the names CAN-2004-0920 to these issues. This is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.
VIII. DISCLOSURE TIMELINE
05/12/2004 Vulnerability acquired by iDEFENSE 06/25/2004 iDEFENSE clients notified 06/29/2004 Initial vendor notification 06/30/2004 Initial vendor response 10/05/2004 Coordinated public disclosure
IX. CREDIT
Kurt Seifried (kurt[at]seifried.org) is credited with this discovery.
Get paid for vulnerability research http://www.idefense.com/poi/teams/vcp.jsp
X. LEGAL NOTICES
Copyright (c) 2004 iDEFENSE, Inc.
Permission is granted for the redistribution of this alert electronically. It may not be edited in any way without the express written consent of iDEFENSE. If you wish to reprint the whole or any part of this alert in any other medium other than electronically, please email customerservice@idefense.com for permission.
Disclaimer: The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
Show details on source website{ "@context": { "@vocab": "https://www.variotdbs.pl/ref/VARIoTentry#", "affected_products": { "@id": "https://www.variotdbs.pl/ref/affected_products" }, "configurations": { "@id": "https://www.variotdbs.pl/ref/configurations" }, "credits": { "@id": "https://www.variotdbs.pl/ref/credits" }, "cvss": { "@id": "https://www.variotdbs.pl/ref/cvss/" }, "description": { "@id": "https://www.variotdbs.pl/ref/description/" }, "exploit_availability": { "@id": "https://www.variotdbs.pl/ref/exploit_availability/" }, "external_ids": { "@id": "https://www.variotdbs.pl/ref/external_ids/" }, "iot": { "@id": "https://www.variotdbs.pl/ref/iot/" }, "iot_taxonomy": { "@id": "https://www.variotdbs.pl/ref/iot_taxonomy/" }, "patch": { "@id": "https://www.variotdbs.pl/ref/patch/" }, "problemtype_data": { "@id": "https://www.variotdbs.pl/ref/problemtype_data/" }, "references": { "@id": "https://www.variotdbs.pl/ref/references/" }, "sources": { "@id": "https://www.variotdbs.pl/ref/sources/" }, "sources_release_date": { "@id": "https://www.variotdbs.pl/ref/sources_release_date/" }, "sources_update_date": { "@id": "https://www.variotdbs.pl/ref/sources_update_date/" }, "threat_type": { "@id": "https://www.variotdbs.pl/ref/threat_type/" }, "title": { "@id": "https://www.variotdbs.pl/ref/title/" }, "type": { "@id": "https://www.variotdbs.pl/ref/type/" } }, "@id": "https://www.variotdbs.pl/vuln/VAR-200411-0163", "affected_products": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/affected_products#", "data": { "@container": "@list" }, "sources": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources#" }, "@id": "https://www.variotdbs.pl/ref/sources" } }, "data": [ { "model": "norton antivirus", "scope": "lte", "trust": 1.0, "vendor": "symantec", "version": "2.1" }, { "model": "norton antivirus", "scope": "eq", "trust": 0.6, "vendor": "symantec", "version": "2.1" }, { "model": "norton antivirus professional edition", "scope": "eq", "trust": 0.3, "vendor": "symantec", "version": "2005" }, { "model": "norton antivirus", "scope": "eq", "trust": 0.3, "vendor": "symantec", "version": "2005" }, { "model": "norton antivirus professional edition", "scope": "eq", "trust": 0.3, "vendor": "symantec", "version": "2004" }, { "model": "norton antivirus", "scope": "eq", "trust": 0.3, "vendor": "symantec", "version": "2004" }, { "model": "norton antivirus professional edition", "scope": "eq", "trust": 0.3, "vendor": "symantec", "version": "2003" }, { "model": "norton antivirus", "scope": "eq", "trust": 0.3, "vendor": "symantec", "version": "20030" } ], "sources": [ { "db": "BID", "id": "11328" }, { "db": "CNNVD", "id": "CNNVD-200411-016" }, { "db": "NVD", "id": "CVE-2004-0920" } ] }, "credits": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/credits#", "sources": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources#" } } }, "data": "iDEFENSE Security Advisory\u203b labs@idefense.com", "sources": [ { "db": "CNNVD", "id": "CNNVD-200411-016" } ], "trust": 0.6 }, "cve": "CVE-2004-0920", "cvss": { "@context": { "cvssV2": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV2#" }, "@id": "https://www.variotdbs.pl/ref/cvss/cvssV2" }, "cvssV3": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV3#" }, "@id": "https://www.variotdbs.pl/ref/cvss/cvssV3/" }, "severity": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/cvss/severity#" }, "@id": "https://www.variotdbs.pl/ref/cvss/severity" }, "sources": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources#" }, "@id": "https://www.variotdbs.pl/ref/sources" } }, "data": [ { "cvssV2": [ { "accessComplexity": "LOW", "accessVector": "NETWORK", "authentication": "NONE", "author": "nvd@nist.gov", "availabilityImpact": "PARTIAL", "baseScore": 5.0, "confidentialityImpact": "NONE", "exploitabilityScore": 10.0, "id": "CVE-2004-0920", "impactScore": 2.9, "integrityImpact": "NONE", "severity": "MEDIUM", "trust": 1.0, "vectorString": "AV:N/AC:L/Au:N/C:N/I:N/A:P", "version": "2.0" }, { "accessComplexity": "LOW", "accessVector": "NETWORK", "authentication": "NONE", "author": "VULHUB", "availabilityImpact": "PARTIAL", "baseScore": 5.0, "confidentialityImpact": "NONE", "exploitabilityScore": 10.0, "id": "VHN-9350", "impactScore": 2.9, "integrityImpact": "NONE", "severity": "MEDIUM", "trust": 0.1, "vectorString": "AV:N/AC:L/AU:N/C:N/I:N/A:P", "version": "2.0" } ], "cvssV3": [], "severity": [ { "author": "nvd@nist.gov", "id": "CVE-2004-0920", "trust": 1.0, "value": "MEDIUM" }, { "author": "CNNVD", "id": "CNNVD-200411-016", "trust": 0.6, "value": "MEDIUM" }, { "author": "VULHUB", "id": "VHN-9350", "trust": 0.1, "value": "MEDIUM" } ] } ], "sources": [ { "db": "VULHUB", "id": "VHN-9350" }, { "db": "CNNVD", "id": "CNNVD-200411-016" }, { "db": "NVD", "id": "CVE-2004-0920" } ] }, "description": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/description#", "sources": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources#" } } }, "data": "Symantec Norton AntiVirus 2004, and earlier versions, allows a virus or other malicious code to avoid detection or cause a denial of service (application crash) using a filename containing an MS-DOS device name. Norton AntiVirus is affected by a scan evasion vulnerability when handling files with MS-DOS reserve device names. This issue is due to a design error that allows the files to avoid being scanned. It should be noted that this vulnerability only arises once the file is already present on a vulnerable computer. All Norton AntiVirus products are able to detect malicious files through incoming email. BACKGROUND\n\nSymantec\u0027s Norton AntiVirus protects email, instant messages, and other\nfiles by automatically removing viruses, worms, and Trojan horses. More\ninformation about the product is available from http://www.symantec.com\n\nII. \n\nThe problem specifically exists in attempts to scan files and\ndirectories named as reserved MS-DOS devices. Reserved MS-DOS device\nnames are a hold over from the original days of Microsoft DOS. The\nreserved MS-DOS device names represent devices such as the first printer\nport (LPT1) and the first serial communication port (COM1). Sample\nreserved MS-DOS device names include AUX, CON, PRN, COM1 and LPT1. reserved device names can be creating with\nstandard Windows utilities by specifying the full Universal Naming\nConvention (UNC) path. The following command will successfully copy a\nfile to the reserved device name \u0027aux\u0027 on the C:\\ drive:\n\n copy source \\\\.\\C:\\aux\n\nIII. ANALYSIS\n\nExploitation allows attackers to evade detection of malicious code. \nAttackers can unpack or decode an otherwise detected malicious payload\nin a stealth manner. \n\nIV. DETECTION\n\niDEFENSE has confirmed the existence of this vulnerability in the latest\nversion of Norton AntiVirus. It is reported that earlier versions crash\nupon parsing files or directories using reserved MS-DOS device names. \n\nV. WORKAROUND\n\nEnsure that no local files or directories using reserved MS-DOS device\nnames exist. On most modern Windows systems there should be no reserved\nMS-DOS device names present. While the Windows search utility can be\nused to locate offending files and directories, either a seperate tool\nor the specification of Universal Naming Convention (UNC) must be used\nto remote them. The following command will successfully remove a file\nstored on the C:\\ drive named \u0027aux\u0027:\n\n del \\\\.\\C:\\aux\n\nVI. VENDOR RESPONSE\n\n\"Symantec engineers have developed a fix for this issue for Symantec\nNorton AntiVirus 2004 that is currently available through LiveUpdate. \nThe fix is being incorporated into all other supported Symantec Norton\nAntiVirus versions and will be available through LiveUpdate when fully\ntested and released.\"\n\nMore information is available in Symantec Security Advisory SYM04-015. \n\nVII. CVE INFORMATION\n\nThe Common Vulnerabilities and Exposures (CVE) project has assigned the\nnames CAN-2004-0920 to these issues. This is a candidate for inclusion\nin the CVE list (http://cve.mitre.org), which standardizes names for\nsecurity problems. \n\nVIII. DISCLOSURE TIMELINE\n\n05/12/2004 Vulnerability acquired by iDEFENSE\n06/25/2004 iDEFENSE clients notified\n06/29/2004 Initial vendor notification\n06/30/2004 Initial vendor response\n10/05/2004 Coordinated public disclosure\n\nIX. CREDIT\n\nKurt Seifried (kurt[at]seifried.org) is credited with this discovery. \n\nGet paid for vulnerability research\nhttp://www.idefense.com/poi/teams/vcp.jsp\n\nX. LEGAL NOTICES\n\nCopyright (c) 2004 iDEFENSE, Inc. \n\nPermission is granted for the redistribution of this alert\nelectronically. It may not be edited in any way without the express\nwritten consent of iDEFENSE. If you wish to reprint the whole or any\npart of this alert in any other medium other than electronically, please\nemail customerservice@idefense.com for permission. \n\nDisclaimer: The information in the advisory is believed to be accurate\nat the time of publishing based on currently available information. Use\nof the information constitutes acceptance for use in an AS IS condition. \nThere are no warranties with regard to this information. Neither the\nauthor nor the publisher accepts any liability for any direct, indirect,\nor consequential loss or damage arising from use of, or reliance on,\nthis information. \n\n_______________________________________________\nFull-Disclosure - We believe in it. \nCharter: http://lists.netsys.com/full-disclosure-charter.html\n", "sources": [ { "db": "NVD", "id": "CVE-2004-0920" }, { "db": "BID", "id": "11328" }, { "db": "VULHUB", "id": "VHN-9350" }, { "db": "PACKETSTORM", "id": "34591" } ], "trust": 1.35 }, "exploit_availability": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/exploit_availability#", "data": { "@container": "@list" }, "sources": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources#" } } }, "data": [ { "reference": "https://www.scap.org.cn/vuln/vhn-9350", "trust": 0.1, "type": "unknown" } ], "sources": [ { "db": "VULHUB", "id": "VHN-9350" } ] }, "external_ids": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/external_ids#", "data": { "@container": "@list" }, "sources": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources#" } } }, "data": [ { "db": "NVD", "id": "CVE-2004-0920", "trust": 2.1 }, { "db": "CNNVD", "id": "CNNVD-200411-016", "trust": 0.7 }, { "db": "XF", "id": "17603", "trust": 0.6 }, { "db": "IDEFENSE", "id": "20041005 SYMANTEC NORTON ANTIVIRUS RESERVED DEVICE NAME HANDLING VULNERABILITY", "trust": 0.6 }, { "db": "BID", "id": "11328", "trust": 0.4 }, { "db": "PACKETSTORM", "id": "34591", "trust": 0.2 }, { "db": "VULHUB", "id": "VHN-9350", "trust": 0.1 } ], "sources": [ { "db": "VULHUB", "id": "VHN-9350" }, { "db": "BID", "id": "11328" }, { "db": "PACKETSTORM", "id": "34591" }, { "db": "CNNVD", "id": "CNNVD-200411-016" }, { "db": "NVD", "id": "CVE-2004-0920" } ] }, "id": "VAR-200411-0163", "iot": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/iot#", "sources": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources#" } } }, "data": true, "sources": [ { "db": "VULHUB", "id": "VHN-9350" } ], "trust": 0.01 }, "last_update_date": "2024-08-14T14:42:20.646000Z", "problemtype_data": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/problemtype_data#", "sources": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources#" } } }, "data": [ { "problemtype": "NVD-CWE-Other", "trust": 1.0 } ], "sources": [ { "db": "NVD", "id": "CVE-2004-0920" } ] }, "references": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/references#", "data": { "@container": "@list" }, "sources": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources#" } } }, "data": [ { "trust": 1.7, "url": "http://www.seifried.org/security/advisories/kssa-010.html" }, { "trust": 1.7, "url": "http://www.idefense.com/application/poi/display?id=147\u0026type=vulnerabilities" }, { "trust": 1.1, "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/17603" }, { "trust": 0.6, "url": "http://xforce.iss.net/xforce/xfdb/17603" }, { "trust": 0.3, "url": "http://www.symantec.com/nav/nav_9xnt/" }, { "trust": 0.3, "url": "http://securityresponse.symantec.com/avcenter/security/content/2004.10.05.html" }, { "trust": 0.3, "url": "http://www.idefense.com/application/poi/display?id=147\u0026type=vulnerabilities\u0026flashstatus=true" }, { "trust": 0.1, "url": "http://www.idefense.com/application/poi/display?id=147\u0026amp;type=vulnerabilities" }, { "trust": 0.1, "url": "http://www.symantec.com" }, { "trust": 0.1, "url": "http://lists.netsys.com/full-disclosure-charter.html" }, { "trust": 0.1, "url": "http://www.idefense.com/poi/teams/vcp.jsp" }, { "trust": 0.1, "url": "https://nvd.nist.gov/vuln/detail/cve-2004-0920" }, { "trust": 0.1, "url": "http://cve.mitre.org)," } ], "sources": [ { "db": "VULHUB", "id": "VHN-9350" }, { "db": "BID", "id": "11328" }, { "db": "PACKETSTORM", "id": "34591" }, { "db": "CNNVD", "id": "CNNVD-200411-016" }, { "db": "NVD", "id": "CVE-2004-0920" } ] }, "sources": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources#", "data": { "@container": "@list" } }, "data": [ { "db": "VULHUB", "id": "VHN-9350" }, { "db": "BID", "id": "11328" }, { "db": "PACKETSTORM", "id": "34591" }, { "db": "CNNVD", "id": "CNNVD-200411-016" }, { "db": "NVD", "id": "CVE-2004-0920" } ] }, "sources_release_date": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources_release_date#", "data": { "@container": "@list" } }, "data": [ { "date": "2004-11-03T00:00:00", "db": "VULHUB", "id": "VHN-9350" }, { "date": "2004-10-05T00:00:00", "db": "BID", "id": "11328" }, { "date": "2004-10-13T03:53:41", "db": "PACKETSTORM", "id": "34591" }, { "date": "2004-10-05T00:00:00", "db": "CNNVD", "id": "CNNVD-200411-016" }, { "date": "2004-11-03T05:00:00", "db": "NVD", "id": "CVE-2004-0920" } ] }, "sources_update_date": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources_update_date#", "data": { "@container": "@list" } }, "data": [ { "date": "2017-07-11T00:00:00", "db": "VULHUB", "id": "VHN-9350" }, { "date": "2009-07-12T07:06:00", "db": "BID", "id": "11328" }, { "date": "2005-10-20T00:00:00", "db": "CNNVD", "id": "CNNVD-200411-016" }, { "date": "2017-07-11T01:30:35.010000", "db": "NVD", "id": "CVE-2004-0920" } ] }, "threat_type": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/threat_type#", "sources": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources#" } } }, "data": "remote", "sources": [ { "db": "PACKETSTORM", "id": "34591" }, { "db": "CNNVD", "id": "CNNVD-200411-016" } ], "trust": 0.7 }, "title": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/title#", "sources": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources#" } } }, "data": "Symantec Norton Antivirus software retains device name handling vulnerability", "sources": [ { "db": "CNNVD", "id": "CNNVD-200411-016" } ], "trust": 0.6 }, "type": { "@context": { "@vocab": "https://www.variotdbs.pl/ref/type#", "sources": { "@container": "@list", "@context": { "@vocab": "https://www.variotdbs.pl/ref/sources#" } } }, "data": "Design Error", "sources": [ { "db": "BID", "id": "11328" }, { "db": "CNNVD", "id": "CNNVD-200411-016" } ], "trust": 0.9 } }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.