{"id": "CVE-2005-2126", "bulletinFamily": "NVD", "title": "CVE-2005-2126", "description": "The FTP client in Windows XP SP1 and Server 2003, and Internet Explorer 6 SP1 on Windows 2000 SP4, when \"Enable Folder View for FTP Sites\" is enabled and the user manually initiates a file transfer, allows user-assisted, remote FTP servers to overwrite files in arbitrary locations via crafted filenames.", "published": "2005-10-21T14:02:00", "modified": "2017-10-10T21:30:14", "cvss": {"score": 2.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:NONE/I:PARTIAL/A:NONE/"}, "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2005-2126", "reporter": "NVD", "references": ["http://support.avaya.com/elmodocs2/security/ASA-2005-214.pdf", "http://www.securiteam.com/windowsntfocus/6M00I0KEAU.html", "http://securitytracker.com/id?1015036", "http://www.kb.cert.org/vuls/id/415828", "http://www.microsoft.com/technet/security/bulletin/ms05-044.mspx"], "cvelist": ["CVE-2005-2126"], "type": "cve", "lastseen": "2017-10-11T11:06:17", "history": [{"bulletin": {"assessment": {"href": "http://oval.mitre.org/repository/data/getDef?id=oval:org.mitre.oval:def:1146", "name": "oval:org.mitre.oval:def:1146", "system": "http://oval.mitre.org/XMLSchema/oval-definitions-5"}, "bulletinFamily": "NVD", "cpe": ["cpe:/a:microsoft:ie:6.0:sp1", "cpe:/o:microsoft:windows_2003_server:r2", "cpe:/o:microsoft:windows_2000::sp4::fr", "cpe:/o:microsoft:windows_xp::sp1:tablet_pc"], "cvelist": ["CVE-2005-2126"], "cvss": {"score": 2.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:NONE/I:PARTIAL/A:NONE/"}, "description": "The FTP client in Windows XP SP1 and Server 2003, and Internet Explorer 6 SP1 on Windows 2000 SP4, when \"Enable Folder View for FTP Sites\" is enabled and the user manually initiates a file transfer, allows user-assisted, remote FTP servers to overwrite files in arbitrary locations via crafted filenames.", "edition": 2, "enchantments": {}, "hash": "38c3fe52118c0b657ea3659e0be636bef55688164b06360d076ebf2a1494a8e6", "hashmap": [{"hash": "601892ece72be3be2f57266ca2354792", "key": "reporter"}, {"hash": "a22390976d3c459a0dbcbd76ddc3ef52", "key": "assessment"}, {"hash": "7de35a348a0562c7c2cac7b36eb3863d", "key": "cvss"}, {"hash": "402c40875ecb606924af9edebeb877a9", "key": "cvelist"}, {"hash": "bbf0e0304382aaf4990d62625f596a4d", "key": "href"}, {"hash": "8357d8344d35dd1bc960ec37664e41dc", "key": "references"}, {"hash": "e150f9593a7df7e0ea89f5edd91afa94", "key": "title"}, {"hash": "dbe248605628b44fbcbbbef31ca50f74", "key": "description"}, {"hash": "1716b5fcbb7121af74efdc153d0166c5", "key": "type"}, {"hash": "da0b2b54a0e2494e267c85ee5f0a1865", "key": "published"}, {"hash": "e65b006e1788abc94c79c04f5d085216", "key": "cpe"}, {"hash": "601892ece72be3be2f57266ca2354792", "key": "bulletinFamily"}, {"hash": "80e65a588d35d3dace4821542acd721b", "key": "scanner"}, {"hash": "4ba68ff6ce83ce5a3b286e94a3475280", "key": "modified"}], "history": [], "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2005-2126", "id": "CVE-2005-2126", "lastseen": "2017-04-18T15:51:18", "modified": "2008-09-10T15:41:06", "objectVersion": "1.2", "published": "2005-10-21T14:02:00", "references": ["http://support.avaya.com/elmodocs2/security/ASA-2005-214.pdf", "http://www.securiteam.com/windowsntfocus/6M00I0KEAU.html", "http://securitytracker.com/id?1015036", "http://www.kb.cert.org/vuls/id/415828", "http://www.microsoft.com/technet/security/bulletin/ms05-044.mspx"], "reporter": "NVD", "scanner": [{"href": "http://oval.mitre.org/repository/data/DownloadDefinition?id=oval:org.mitre.oval:def:1416", "name": "oval:org.mitre.oval:def:1416", "system": "http://oval.mitre.org/XMLSchema/oval-definitions-5"}], "title": "CVE-2005-2126", "type": "cve", "viewCount": 1}, "differentElements": ["assessment", "modified"], "edition": 2, "lastseen": "2017-04-18T15:51:18"}, {"bulletin": {"assessment": {"href": "http://oval.mitre.org/repository/data/getDef?id=oval:org.mitre.oval:def:1416", "name": "oval:org.mitre.oval:def:1416", "system": "http://oval.mitre.org/XMLSchema/oval-definitions-5"}, "bulletinFamily": "NVD", "cpe": ["cpe:/a:microsoft:ie:6.0:sp1", "cpe:/o:microsoft:windows_2003_server:r2", "cpe:/o:microsoft:windows_2000::sp4::fr", "cpe:/o:microsoft:windows_xp::sp1:tablet_pc"], "cvelist": ["CVE-2005-2126"], "cvss": {"score": 2.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:NONE/I:PARTIAL/A:NONE/"}, "description": "The FTP client in Windows XP SP1 and Server 2003, and Internet Explorer 6 SP1 on Windows 2000 SP4, when \"Enable Folder View for FTP Sites\" is enabled and the user manually initiates a file transfer, allows user-assisted, remote FTP servers to overwrite files in arbitrary locations via crafted filenames.", "edition": 1, "hash": "f358901ae647e13b9529e1f6a8bd4805a97e8bd69cd8eb9f030e9d764105e093", "hashmap": [{"hash": "601892ece72be3be2f57266ca2354792", "key": "reporter"}, {"hash": "56765472680401499c79732468ba4340", "key": "objectVersion"}, {"hash": "7de35a348a0562c7c2cac7b36eb3863d", "key": "cvss"}, {"hash": "402c40875ecb606924af9edebeb877a9", "key": "cvelist"}, {"hash": "bbf0e0304382aaf4990d62625f596a4d", "key": "href"}, {"hash": "8357d8344d35dd1bc960ec37664e41dc", "key": "references"}, {"hash": "3c9d8685187ee2e11bce455515010f43", "key": "assessment"}, {"hash": "e150f9593a7df7e0ea89f5edd91afa94", "key": "title"}, {"hash": "dbe248605628b44fbcbbbef31ca50f74", "key": "description"}, {"hash": "1716b5fcbb7121af74efdc153d0166c5", "key": "type"}, {"hash": "da0b2b54a0e2494e267c85ee5f0a1865", "key": "published"}, {"hash": "e65b006e1788abc94c79c04f5d085216", "key": "cpe"}, {"hash": "601892ece72be3be2f57266ca2354792", "key": "bulletinFamily"}, {"hash": "80e65a588d35d3dace4821542acd721b", "key": "scanner"}, {"hash": "4ba68ff6ce83ce5a3b286e94a3475280", "key": "modified"}], "history": [], "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2005-2126", "id": "CVE-2005-2126", "lastseen": "2016-09-03T05:34:59", "modified": "2008-09-10T15:41:06", "objectVersion": "1.2", "published": "2005-10-21T14:02:00", "references": ["http://support.avaya.com/elmodocs2/security/ASA-2005-214.pdf", "http://www.securiteam.com/windowsntfocus/6M00I0KEAU.html", "http://securitytracker.com/id?1015036", "http://www.kb.cert.org/vuls/id/415828", "http://www.microsoft.com/technet/security/bulletin/ms05-044.mspx"], "reporter": "NVD", "scanner": [{"href": "http://oval.mitre.org/repository/data/DownloadDefinition?id=oval:org.mitre.oval:def:1416", "name": "oval:org.mitre.oval:def:1416", "system": "http://oval.mitre.org/XMLSchema/oval-definitions-5"}], "title": "CVE-2005-2126", "type": "cve", "viewCount": 0}, "differentElements": ["assessment"], "edition": 1, "lastseen": "2016-09-03T05:34:59"}], "edition": 3, "hashmap": [{"key": "assessment", "hash": "399c2fce9a3b60ad47ee4484423814a0"}, {"key": "bulletinFamily", "hash": "601892ece72be3be2f57266ca2354792"}, {"key": "cpe", "hash": "e65b006e1788abc94c79c04f5d085216"}, {"key": "cvelist", "hash": "402c40875ecb606924af9edebeb877a9"}, {"key": "cvss", "hash": "7de35a348a0562c7c2cac7b36eb3863d"}, {"key": "description", "hash": "dbe248605628b44fbcbbbef31ca50f74"}, {"key": "href", "hash": "bbf0e0304382aaf4990d62625f596a4d"}, {"key": "modified", "hash": "9d9970a67ff80afa5b2ab7d0e599370e"}, {"key": "published", "hash": "da0b2b54a0e2494e267c85ee5f0a1865"}, {"key": "references", "hash": "8357d8344d35dd1bc960ec37664e41dc"}, {"key": "reporter", "hash": "601892ece72be3be2f57266ca2354792"}, {"key": "scanner", "hash": "80e65a588d35d3dace4821542acd721b"}, {"key": "title", "hash": "e150f9593a7df7e0ea89f5edd91afa94"}, {"key": "type", "hash": "1716b5fcbb7121af74efdc153d0166c5"}], "hash": "a8d491b147bda5e50cf4da7721088ed7a4c0b8fbe4582d90a9a52ec91931c33c", "viewCount": 1, "enchantments": {"score": {"value": 4.3, "vector": "NONE", "modified": "2017-10-11T11:06:17"}, "vulnersScore": 4.3}, "objectVersion": "1.3", "cpe": ["cpe:/a:microsoft:ie:6.0:sp1", "cpe:/o:microsoft:windows_2003_server:r2", "cpe:/o:microsoft:windows_2000::sp4::fr", "cpe:/o:microsoft:windows_xp::sp1:tablet_pc"], "assessment": {"href": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A1146", "name": "oval:org.mitre.oval:def:1146", "system": "http://oval.mitre.org/XMLSchema/oval-definitions-5"}, "scanner": [{"href": "http://oval.mitre.org/repository/data/DownloadDefinition?id=oval:org.mitre.oval:def:1416", "name": "oval:org.mitre.oval:def:1416", "system": "http://oval.mitre.org/XMLSchema/oval-definitions-5"}]}

{"cert": [{"lastseen": "2018-08-31T02:36:34", "references": ["http://web.nvd.nist.gov/view/vuln/detail?vulnId=CAN-2005-2126", "http://www.microsoft.com/technet/security/Bulletin/MS05-044.mspx", "http://www.microsoft.com/technet/security/Bulletin/MS05-044.mspx", "http://www.microsoft.com/technet/security/Bulletin/MS05-044.mspx", "http://secunia.com/advisories/17163/"], "description": "### Overview\n\nAn input validation error in the Microsoft Windows FTP Client may allow a remote attacker to write files to arbitrary locations and may allow the execution of arbitrary code.\n\n### Description\n\nThe Microsoft Windows FTP Client does not properly validate the names of received files. If a remote attacker can persuade a user to download a file with a specially crafted name using the Windows FTP Client, that attacker may be able to write that file to an arbitrary location on the users system. In order to exploit this vulnerability, the crafted file name must map to an existing location on the user's system. \n\nNote that this vulnerability may allow a remote attacker to execute arbitrary code. For instance, an attacker may be able to leverage this vulnerability to download an arbitrary file to the Startup folder. If the downloaded file is executable, then that file will be executed the next time a user logs in. \n \nFor more information, including a list of affected software, please see [MS05-044](<http://www.microsoft.com/technet/security/Bulletin/MS05-044.mspx>). Please note that exploit code for this vulnerability is publicly available. \n \n--- \n \n### Impact\n\nA remote attacker may be able to write files to arbitrary locations on a vulnerable system. If the target location is the Startup folder, then it is possible to cause arbitrary code to be automatically executed the next time the user logs in. \n \n--- \n \n### Solution\n\n**Apply a patch**\n\nMicrosoft has addressed this issue in Microsoft Security Bulletin [MS05-044](<http://www.microsoft.com/technet/security/Bulletin/MS05-044.mspx>) \n \n--- \n \n**Do not download files from untrusted source****s**\n\n \nBy only downloading files from trusted sources, the chances of exploitation are reduced. \n \n--- \n \n### Systems Affected \n\nVendor| Status| Date Notified| Date Updated \n---|---|---|--- \nMicrosoft Corporation| | -| 12 Oct 2005 \nIf you are a vendor and your product is affected, [let us know](<mailto:cert@cert.org?Subject=VU%23415828 Vendor Status Inquiry>).\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | N/A | N/A \nTemporal | N/A | N/A \nEnvironmental | N/A | N/A \n \n### References\n\n * <http://www.microsoft.com/technet/security/Bulletin/MS05-044.mspx>\n * <http://secunia.com/advisories/17163/>\n\n### Credit\n\nThis vulnerability was reported by Microsoft in MS05-044 .\n\nThis document was written by Jeff Gennari.\n\n### Other Information\n\n * CVE IDs: [CAN-2005-2126](<http://web.nvd.nist.gov/view/vuln/detail?vulnId=CAN-2005-2126>)\n * Date Public: 11 Oct 2005\n * Date First Published: 13 Oct 2005\n * Date Last Updated: 14 Oct 2005\n * Severity Metric: 16.20\n * Document Revision: 40\n\n", "edition": 4, "reporter": "CERT", "published": "2005-10-13T00:00:00", "title": "Microsoft Windows FTP client does not properly validate received file names", "type": "cert", "enchantments": {"score": {"vector": "NONE", "value": 6.8}}, "bulletinFamily": "info", "cvelist": ["CVE-2005-2126", "CVE-2005-2126"], "modified": "2005-10-14T00:00:00", "id": "VU:415828", "href": "https://www.kb.cert.org/vuls/id/415828", "cvss": {"score": 2.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:NONE/I:PARTIAL/A:NONE/"}}], "osvdb": [{"lastseen": "2017-04-28T13:20:16", "references": [], "edition": 1, "description": "# No description provided by the source\n\n## References:\n[Vendor Specific Advisory URL](http://www130.nortelnetworks.com/cgi-bin/eserv/cs/main.jsp?cscat=BLTNDETAIL&DocumentOID=361442&RenditionID=)\nSecurity Tracker: 1015036\n[Secunia Advisory ID:17223](https://secuniaresearch.flexerasoftware.com/advisories/17223/)\n[Secunia Advisory ID:17163](https://secuniaresearch.flexerasoftware.com/advisories/17163/)\nOther Advisory URL: http://support.avaya.com/elmodocs2/security/ASA-2005-214.pdf\nOther Advisory URL: http://www.securiteam.com/windowsntfocus/6M00I0KEAU.html\nOther Advisory URL: http://www.auscert.org.au/render.html?it=5592\nMicrosoft Security Bulletin: MS05-044\nMicrosoft Knowledge Base Article: 905495\nKeyword: 2005006318\nGeneric Exploit URL: http://www.frsirt.com/exploits/20051013.ms05-044.c.php\nFrSIRT Advisory: ADV-2005-2041\n[CVE-2005-2126](https://vulners.com/cve/CVE-2005-2126)\nCERT VU: 415828\nBugtraq ID: 12160\n", "reporter": "OSVDB", "published": "2005-10-11T21:02:46", "type": "osvdb", "title": "Microsoft Windows FTP Client Arbitrary File Write", "enchantments": {"score": {"vector": "NONE", "value": 5.0}}, "bulletinFamily": "software", "affectedSoftware": [], "cvelist": ["CVE-2005-2126"], "modified": "2005-10-11T21:02:46", "href": "https://vulners.com/osvdb/OSVDB:19901", "id": "OSVDB:19901", "cvss": {"score": 2.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:NONE/I:PARTIAL/A:NONE/"}}], "securityvulns": [{"lastseen": "2018-08-31T11:10:14", "references": [], "description": "Microsoft Security Bulletin MS05-044\r\nVulnerability in the Windows FTP Client Could Allow File Transfer Location Tampering &#40;905495&#41;\r\nPublished: October 11, 2005\r\n\r\nVersion: 1.0\r\nSummary\r\n\r\nWho should read this document: Customers who use Microsoft Windows\r\n\r\nImpact of Vulnerability: Tampering\r\n\r\nMaximum Severity Rating: Moderate\r\n\r\nRecommendation: Customers should consider applying the security update.\r\n\r\nSecurity Update Replacement: None\r\n\r\nCaveats: None\r\n\r\nTested Software and Security Update Download Locations:\r\n\r\nAffected Software:\r\n\u2022\t\r\n\r\nMicrosoft Windows XP Service Pack 1 - Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 - Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 for Itanium-based Systems \u2013 Download the update\r\n\r\nAffected Components:\r\n\u2022\t\r\n\r\nInternet Explorer 6 Service Pack 1 on Microsoft Windows 2000 Service Pack 4 \u2013 Download the update\r\n\r\nNon-Affected Software:\r\n\u2022\t\r\n\r\nMicrosoft Windows 2000 Service Pack 4\r\n\u2022\t\r\n\r\nMicrosoft Windows XP Service Pack 2\r\n\u2022\t\r\n\r\nMicrosoft Windows XP Professional x64 Edition\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 Service Pack 1\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 with SP1 for Itanium-based Systems\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 x64 Edition\r\n\u2022\t\r\n\r\nMicrosoft Windows 98, Microsoft Windows 98 Second Edition &#40;SE&#41;, and Microsoft Windows Millennium Edition &#40;ME&#41;\r\n\r\nNon-Affected Components:\r\n\u2022\t\r\n\r\nInternet Explorer 5.01 Service Pack 4 on Microsoft Windows 2000 Service Pack 4\r\n\r\nThe software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.\r\nTop of sectionTop of section\r\nGeneral Information\r\n\t\r\nExecutive Summary\r\n\r\nExecutive Summary:\r\n\r\nThis update resolves a newly-discovered, public vulnerability. A vulnerability exists in the Windows FTP client because of the way it validates file names. This vulnerability could allow an attacker to tamper with the file transfer location on the client during an FTP file transfer session.\r\n\r\nThe vulnerability is documented in the \u201cVulnerability Details\u201d section of this bulletin.\r\n\r\nWe recommend that customers consider applying the security update.\r\n\r\nSeverity Ratings and Vulnerability Identifiers:\r\nVulnerability Identifiers\tImpact of Vulnerability\tWindows XP Service Pack 1\tWindows Server 2003\tInternet Explorer 6 Service Pack 1 When Installed On Windows 2000 Service Pack 4\r\n\r\nFTP Client Vulnerability - CAN-2005-2126\r\n\t\r\n\r\nTampering\r\n\t\r\n\r\nModerate\r\n\t\r\n\r\nModerate\r\n\t\r\n\r\nModerate\r\n\r\nThis assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.\r\n\r\nNote The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:\r\n\u2022\t\r\n\r\nThe Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.\r\nTop of sectionTop of section\r\n\t\r\nFrequently asked questions &#40;FAQ&#41; related to this security update\r\n\r\nExtended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I am still using one of these operating systems, what should I do?\r\n\r\nWindows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.\r\n\r\nCustomers who require additional custom support for these products must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager.\r\n\r\nFor more information, see the Windows Operating System Product Support Lifecycle FAQ.\r\n\r\nSecurity update support for Microsoft Windows XP 64-Bit Edition Service Pack 1 &#40;Itanium&#41; and Microsoft Windows XP 64-Bit Edition Version 2003 &#40;Itanium&#41; ended on June 30, 2005. I\u2019m still using one of these operating systems, what should I do?\r\n\r\nWith the release of Windows XP Professional x64 Edition, Microsoft Windows XP 64-Bit Edition Service Pack 1 &#40;Itanium&#41; and Microsoft Windows XP 64-Bit Edition Version 2003 &#40;Itanium&#41; will no longer receive security update support. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. Microsoft will continue to fully support Windows Server 2003 for Itanium-based systems, Windows XP Professional x64 Edition, and Windows Server 2003 x64 Editions for 64-bit computing requirements. Microsoft continues to license and support Windows Server 2003 Enterprise and Datacenter editions for Itanium-based systems, and the 64-bit version of SQL Server 2000 Enterprise Edition. In the future we will expand Itanium support to Visual Studio 2005, .NET Framework 2005 and SQL Server 2005.\r\n\r\nCustomers who require additional assistance about this issue must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for information about the available migration options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager.\r\n\r\nCan I use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; 1.2.1 to determine whether this update is required?\r\n\r\nYes. MBSA 1.2.1 will determine whether this update is required for Windows XP Service Pack 1 and for Windows Server 2003. For more information about MBSA, visit the MBSA Web site.\r\nMBSA 1.2.1 does not support detection for this vulnerability on Windows 2000 Service Pack 4. For more information about the programs that MBSA 1.2.1 currently does not detect, see Microsoft Knowledge Base Article 306460. However, Microsoft has developed a version of the Enterprise Update Scanning Tool &#40;EST&#41; that will help customers determine if the security updates that are provided in this security bulletin are required. For more information, see the &quot;Can I use a version of the Enterprise Update Scanning Tool &#40;EST&#41; to determine whether this update is required?&quot; question in the FAQ section of this bulletin.\r\n\r\nWhat is the Enterprise Update Scanning Tool &#40;EST&#41;?\r\n\r\nAs part of an ongoing commitment to provide detection tools for bulletin-class security updates, Microsoft delivers a stand-alone detection tool whenever the Microsoft Baseline Security Analyzer &#40;MBSA&#41; and the Office Detection Tool &#40;ODT&#41; cannot detect whether the update is required for an MSRC release cycle. This stand-alone tool is called the Enterprise Update Scanning Tool &#40;EST&#41; and is designed for enterprise administrators. When a version of the Enterprise Update Scanning Tool is created for a specific bulletin, customers can run the tool from a command line interface &#40;CLI&#41; and view the results of the XML output file. To help customers better utilize the tool, detailed documentation will be provided with the tool. There is also a version of the tool that offers an integrated experience for SMS administrators.\r\n\r\nCan I use a version of the Enterprise Update Scanning Tool &#40;EST&#41; to determine whether this update is required?\r\n\r\nYes. Microsoft has created a version of the EST that will determine if you have to apply this update. For download links and more information about the version of the EST that is being released this month, visit the following Microsoft Web site. SMS customers should review the &quot;Can I use Systems Management Server &#40;SMS&#41; to determine whether this update is required?&quot; question in the FAQ section of this bulletin for more information about SMS and EST.\r\n\r\nCan I use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; 2.0 to determine whether this update is required?\r\n\r\nYes. MBSA 2.0 will determine whether this update is required. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about MBSA, visit the MBSA Web site.\r\n\r\nCan I use Systems Management Server &#40;SMS&#41; to determine whether this update is required?\r\n\r\nYes. SMS can help detect and deploy this security update. SMS uses MBSA for detection; therefore, SMS has the same limitation listed earlier in this bulletin related to programs that MBSA does not detect.\r\n\r\nHowever, the SMS Extended Security Update Inventory Tool is a version of the EST that SMS customers can obtain that offers an integrated experience for SMS administrators. To download this version of the EST, visit the following Microsoft Web site. This tool may also be available for SMS customers from the SMS Web site.\r\n\r\nThe Security Update Inventory Tool can be used by SMS for detecting security updates that are offered by Windows Update, that are supported by Software Update Services, and other security updates that are supported by MBSA 1.2.1. For more information about the Security Update Inventory Tool, see the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460.\r\n\r\nThe SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS for detecting security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, see the following Microsoft Web site.\r\n\r\nFor more information about SMS, visit the SMS Web site.\r\nTop of sectionTop of section\r\n\t\r\nVulnerability Details\r\n\t\r\nFTP Client Vulnerability - CAN-2005-2126:\r\n\r\nA tampering vulnerability exists in the Windows FTP client. This vulnerability could allow an attacker to modify the intended destination location for a file transfer, when a client has manually chosen to transfer a file by using FTP. This vulnerability could allow the attacker to write the file to any file system that is located on an affected system.\r\n\t\r\nMitigating Factors for FTP Client Vulnerability - CAN-2005-2126:\r\n\u2022\t\r\n\r\nIf an attacker successfully persuades users to visit an FTP server hosting files with specially-crafted file names, the attacker would have no way of forcing files to be transferred. User interaction is required before the file can be transferred to the affected system.\r\n\u2022\t\r\n\r\nIf the malicious FTP transfer tries to overwrite an existing file on the affected system, the user receives an \u201cOverwrite File\u201d warning message. The file is saved only if the user selects to allow it to save when they receive the warning message.\r\n\u2022\t\r\n\r\nBy default, the \u201cEnable Folder View for FTP Sites\u201d Internet Explorer setting is disabled on all affected operating system versions. An attacker would only be successful if the user manually enables the \u201cEnable Folder View for FTP Sites\u201d Internet Explorer setting on the affected system.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for FTP Client Vulnerability - CAN-2005-2126:\r\n\r\nMicrosoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.\r\n\u2022\t\r\n\r\nDo not download files from un-trusted FTP servers\r\n\r\nYou can mitigate the risk of attack by downloading files only from FTP servers that you trust.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for FTP Client Vulnerability - CAN-2005-2126:\r\n\r\nWhat is the scope of the vulnerability?\r\nThis is a tampering vulnerability. This vulnerability could allow an attacker to modify the intended destination location for a file transfer when a client has manually chosen to transfer a file by using FTP.\r\n\r\nWhat causes the vulnerability?\r\nThe Windows FTP client does not properly validate file names that are received from FTP servers.\r\n\r\nWhat might an attacker use the vulnerability to do?\r\nAn attacker who exploited this vulnerability could save files to specific locations on an affected system. These files could allow other attacks. For example, an attacker could save an executable file in the \u201cStartup\u201d folder. Then, the transferred file would run the next time the user logs on.\r\n\r\nWho could exploit the vulnerability?\r\nAnyone who could persuade a user to visit and transfer files from an FTP server that hosts files that have specially-crafted file names.\r\n\r\nHow could an attacker exploit the vulnerability?\r\nAn attacker could exploit this vulnerability by hosting a file on an FTP server that has a specially-crafted file name. The file name must be constructed in such a way that it bypasses the file name validation that the FTP client provides and that it maps to a valid location on the users computer. An attacker must then persuade a user to download this file.\r\n\r\nCan the vulnerability be exploited automatically by visiting an FTP server?\r\nNo. User interaction is required for the file to be transferred and saved by using FTP.\r\n\r\nWhat systems are primarily at risk from the vulnerability?\r\nThe vulnerability requires that a user connect to an FTP server and transfer files from the FTP server. Therefore, any systems where FTP transfers occur frequently, such as workstations, are at the most risk from this vulnerability. Systems that are not typically used to visit FTP servers, such as most server systems, are at a reduced risk.\r\n\r\nWhat does the update do?\r\nThe update removes the vulnerability by modifying the way the Windows FTP client validates file names that it receives from FTP servers.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed?\r\nYes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CAN-2005-2126\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?\r\nNo. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers. However, examples of proof of concept code had been published when this security bulletin was originally issued.\r\n\r\nDoes applying this security update help protect customers from the code that has been published publicly that tries to exploit this vulnerability?\r\nYes. This security update addresses the vulnerability for which proof of concept code has been published.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nSecurity Update Information\r\n\r\nAffected Software:\r\n\r\nFor information about the specific security update for your affected software, click the appropriate link:\r\n\t\r\nWindows Server 2003\r\n\r\nPrerequisites\r\nThis security update requires a release version of Windows Server 2003.\r\n\r\nInclusion in Future Service Packs:\r\nThe update for this issue will be included in future Service Pack or Update Rollup.\r\n\r\nInstallation Information\r\n\r\nThis security update supports the following setup switches.\r\nSupported Security Update Installation Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and force other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nPresents a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplays a dialog box prompting the local user to allow a restart\r\nSpecial Options\t \r\n\r\n/overwriteoem\r\n\t\r\n\r\nOverwrites OEM files without prompting\r\n\r\n/nobackup\r\n\t\r\n\r\nDoes not back up files needed for uninstall\r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down\r\n\r\n/log: path\r\n\t\r\n\r\nAllows the redirection of installation log files\r\n\r\n/integrate:path\r\n\t\r\n\r\nIntegrates the update into the Windows source files. These files are located at the path that is specified in the switch.\r\n\r\n/extract[:path]\r\n\t\r\n\r\nExtracts files without starting the Setup program\r\n\r\n/ER\r\n\t\r\n\r\nEnables extended error reporting\r\n\r\n/verbose\r\n\t\r\n\r\nEnables verbose logging. During installation, creates &#37;Windir&#37;&#92;CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.\r\n\r\nNote You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nDeployment Information\r\n\r\nTo install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:\r\n\r\nWindowsserver2003-kb905495-x86-enu /quiet\r\n\r\nNote Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB905495.log file for any failure messages when they use this switch.\r\n\r\nTo install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:\r\n\r\nWindowsserver2003-kb905495-x86-enu /norestart\r\n\r\nFor information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.\r\n\r\nRestart Requirement\r\n\r\nIn some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012\r\n\r\nRemoval Information\r\n\r\nTo remove this update, use the Add or Remove Programs tool in Control Panel.\r\n\r\nSystem administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the &#37;Windir&#37;&#92;$NTUninstallKB905495$&#92;Spuninst folder.\r\nSupported Spuninst.exe Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and force other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nPresents a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplays a dialog box prompting the local user to allow a restart\r\nSpecial Options\t \r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files\r\n\r\nFile Information\r\n\r\nThe English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time &#40;UTC&#41;. When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.\r\n\r\nWindows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003:\r\nFile Name\tVersion\tDate\tTime\tSize\tFolder\r\n\r\nMsieftp.dll\r\n\t\r\n\r\n6.0.3790.383\r\n\t\r\n\r\n06-Aug-2005\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n236,032\r\n\t\r\n\r\nRTMGDR\r\n\r\nMsieftp.dll\r\n\t\r\n\r\n6.0.3790.383\r\n\t\r\n\r\n06-Aug-2005\r\n\t\r\n\r\n04:25\r\n\t\r\n\r\n236,032\r\n\t\r\n\r\nRTMQFE\r\n\r\nArpidfix.exe\r\n\t\r\n\r\n5.2.3790.383\r\n\t\r\n\r\n06-Aug-2005\r\n\t\r\n\r\n02:04\r\n\t\r\n\r\n30,208\r\n\t\r\n\r\nWindows Server 2003, Enterprise Edition for Itanium-based Systems and Windows Server 2003, Datacenter Edition for Itanium-based Systems:\r\nFile Name\tVersion\tDate\tTime\tSize\tCPU\tFolder\r\n\r\nMsieftp.dll\r\n\t\r\n\r\n6.0.3790.383\r\n\t\r\n\r\n06-Aug-2005\r\n\t\r\n\r\n04:10\r\n\t\r\n\r\n548,864\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMGDR\r\n\r\nWmsieftp.dll\r\n\t\r\n\r\n6.0.3790.383\r\n\t\r\n\r\n06-Aug-2005\r\n\t\r\n\r\n04:18\r\n\t\r\n\r\n236,032\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nRTMGDR&#92;WOW\r\n\r\nMsieftp.dll\r\n\t\r\n\r\n6.0.3790.383\r\n\t\r\n\r\n06-Aug-2005\r\n\t\r\n\r\n04:19\r\n\t\r\n\r\n548,864\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMQFE\r\n\r\nWmsieftp.dll\r\n\t\r\n\r\n6.0.3790.383\r\n\t\r\n\r\n06-Aug-2005\r\n\t\r\n\r\n04:25\r\n\t\r\n\r\n236,032\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nRTMQFE&#92;WOW\r\n\r\nArpidfix.exe\r\n\t\r\n\r\n5.2.3790.383\r\n\t\r\n\r\n06-Aug-2005\r\n\t\r\n\r\n01:51\r\n\t\r\n\r\n67,072\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nNotes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.\r\n\r\nIf you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.\r\n\r\nFor more information about this behavior, see Microsoft Knowledge Base Article 824994.\r\n\r\nFor more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nFor more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.\r\n\r\nArpidfix.exe is used by the security update installer to address an issue documented in Microsoft Knowledge Base Article 904630. This file is not installed onto the affected system.\r\n\r\nVerifying that the Update Has Been Applied\r\n\u2022\t\r\n\r\nMicrosoft Baseline Security Analyzer\r\n\r\nTo verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.\r\n\u2022\t\r\n\r\nFile Version Verification\r\n\r\nNote Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, and then click Search.\r\n\r\n2.\r\n\t\r\n\r\nIn the Search Results pane, click All files and folders under Search Companion.\r\n\r\n3.\r\n\t\r\n\r\nIn the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.\r\n\r\n4.\r\n\t\r\n\r\nIn the list of files, right-click a file name from the appropriate file information table, and then click Properties.\r\n\r\nNote Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.\r\n\r\n5.\r\n\t\r\n\r\nOn the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.\r\n\r\nNote Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.\r\n\u2022\t\r\n\r\nRegistry Key Verification\r\n\r\nYou may also be able to verify the files that this security update has installed by reviewing the following registry keys.\r\n\r\nWindows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Enterprise Edition for Itanium-based Systems; and Windows Server 2003, Datacenter Edition for Itanium-based Systems:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows Server 2003&#92;SP1&#92;KB905495&#92;Filelist\r\n\r\nNote This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly if an administrator or an OEM integrates or slipstreams the 905495 security update into the Windows installation source files.\r\nTop of sectionTop of section\r\n\t\r\nWindows XP Service Pack 1\r\n\r\nPrerequisites\r\nThis security update requires Microsoft Windows XP Service Pack 1. For more information, see Microsoft Knowledge Base Article 322389.\r\n\r\nInclusion in Future Service Packs:\r\nThe update for this issue will be included in a future Service Pack or Update Rollup.\r\n\r\nInstallation Information\r\n\r\nThis security update supports the following setup switches.\r\nSupported Security Update Installation Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and force other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nPresents a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplays a dialog box prompting the local user to allow a restart\r\nSpecial Options\t \r\n\r\n/overwriteoem\r\n\t\r\n\r\nOverwrites OEM files without prompting\r\n\r\n/nobackup\r\n\t\r\n\r\nDoes not back up files needed for uninstall\r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files\r\n\r\n/integrate:path\r\n\t\r\n\r\nIntegrates the update into the Windows source files. These files are located at the path that is specified in the switch.\r\n\r\n/extract[:path]\r\n\t\r\n\r\nExtracts files without starting the Setup program\r\n\r\n/ER\r\n\t\r\n\r\nEnables extended error reporting\r\n\r\n/verbose\r\n\t\r\n\r\nEnables verbose logging. During installation, creates &#37;Windir&#37;&#92;CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.\r\n\r\nNote You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nDeployment Information\r\n\r\nTo install the security update without any user intervention, use the following command at a command prompt for Microsoft Windows XP:\r\n\r\nWindowsxp-kb905495-x86-enu /quiet\r\n\r\nNote Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB905495.log file for any failure messages when they use this switch.\r\n\r\nTo install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:\r\n\r\nWindowsxp-kb905495-x86-enu /norestart\r\n\r\nFor information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.\r\n\r\nRestart Requirement\r\n\r\nYou must restart your system after you apply this security update. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.\r\n\r\nRemoval Information\r\n\r\nTo remove this security update, use the Add or Remove Programs tool in Control Panel.\r\n\r\nSystem administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the &#37;Windir&#37;&#92;$NTUninstallKB905495$&#92;Spuninst folder.\r\nSupported Spuninst.exe Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and force other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nPresents a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplays a dialog box prompting the local user to allow a restart\r\nSpecial Options\t \r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files\r\n\r\nFile Information\r\n\r\nThe English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time &#40;UTC&#41;. When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.\r\n\r\nWindows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition:\r\nFile Name\tVersion\tDate\tTime\tSize\r\n\r\nMsieftp.dll\r\n\t\r\n\r\n6.0.2800.1724\r\n\t\r\n\r\n05-Aug-2005\r\n\t\r\n\r\n17:23\r\n\t\r\n\r\n230,400\r\n\r\nArpidfix.exe\r\n\t\r\n\r\n5.1.2600.1735\r\n\t\r\n\r\n24-Aug-2005\r\n\t\r\n\r\n04:53\r\n\t\r\n\r\n27,648\r\n\r\nNotes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.\r\n\r\nIf you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.\r\n\r\nFor more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nFor more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.\r\n\r\nArpidfix.exe is used by the security update installer to address an issue documented in Microsoft Knowledge Base Article 904630. This file is not installed onto the affected system.\r\n\r\nVerifying that the Update Has Been Applied\r\n\u2022\t\r\n\r\nMicrosoft Baseline Security Analyzer\r\n\r\nTo verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.\r\n\u2022\t\r\n\r\nFile Version Verification\r\n\r\nNote Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, and then click Search.\r\n\r\n2.\r\n\t\r\n\r\nIn the Search Results pane, click All files and folders under Search Companion.\r\n\r\n3.\r\n\t\r\n\r\nIn the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.\r\n\r\n4.\r\n\t\r\n\r\nIn the list of files, right-click a file name from the appropriate file information table, and then click Properties.\r\n\r\nNote Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.\r\n\r\n5.\r\n\t\r\n\r\nOn the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.\r\n\r\nNote Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.\r\n\u2022\t\r\n\r\nRegistry Key Verification\r\n\r\nYou may also be able to verify the files that this security update has installed by reviewing the following registry keys.\r\n\r\nFor Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows XP&#92;SP2&#92;KB905495&#92;Filelist\r\n\r\nFor Windows XP Professional x64 Edition:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows XP Version 2003&#92;SP2&#92;KB905495&#92;Filelist\r\n\r\nNote These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly if an administrator or an OEM integrates or slipstreams the 905495 security update into the Windows installation source files.\r\nTop of sectionTop of section\r\n\t\r\nInternet Explorer 6 Service Pack 1 Windows 2000 Service Pack 4\r\n\r\nPrerequisites\r\nTo install the Internet Explorer 6 Service Pack 1 &#40;SP1&#41; version of this update, you must be running Internet Explorer 6 SP1 &#40;version 6.00.2800.1106&#41; on one of the following versions of Windows:\r\n\u2022\t\r\n\r\nMicrosoft Windows 2000 Service Pack 3 or Windows 2000 Service Pack 4\r\n\u2022\t\r\n\r\nMicrosoft Small Business Server 2000 Service Pack 1a &#40;SP1a&#41; or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 &#40;SP4&#41;.\r\n\r\nThe software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.\r\n\r\nFor more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.\r\n\r\nInclusion in Future Service Packs:\r\nThe update for this issue may be included in a future Update Rollup.\r\n\r\nInstallation Information\r\n\r\nThis security update supports the following setup switches.\r\nSupported Security Update Installation Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and force other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nPresents a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplays a dialog box prompting the local user to allow a restart\r\nSpecial Options\t \r\n\r\n/overwriteoem\r\n\t\r\n\r\nOverwrites OEM files without prompting\r\n\r\n/nobackup\r\n\t\r\n\r\nDoes not back up files needed for uninstall\r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files\r\n\r\n/extract[:path]\r\n\t\r\n\r\nExtracts files without starting the Setup program\r\n\r\n/ER\r\n\t\r\n\r\nEnables extended error reporting\r\n\r\n/verbose\r\n\t\r\n\r\nEnables verbose logging. During installation, creates &#37;Windir&#37;&#92;CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.\r\n\r\nNote You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.\r\n\r\nDeployment Information\r\n\r\nTo install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 4:\r\n\r\nIE6.0sp1-KB905495-Windows2000-x86-enu /quiet\r\n\r\nNote Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB905495.log file for any failure messages when they use this switch.\r\n\r\nTo install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 4:\r\n\r\nIE6.0sp1-KB905495-Windows2000-x86-enu /norestart\r\n\r\nFor information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.\r\n\r\nRestart Requirement\r\n\r\nYou must restart your system after you apply this security update.\r\n\r\nRemoval Information\r\n\r\nTo remove this security update, use the Add or Remove Programs tool in Control Panel.\r\n\r\nSystem administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the &#37;Windir&#37;&#92;$NTUninstallKB905495$&#92;Spuninst folder.\r\nSupported Spuninst.exe Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and force other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nPresents a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplay a dialog box prompting the local user to allow a restart\r\nSpecial Options\t \r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files\r\n\r\nFile Information\r\n\r\nThe English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time &#40;UTC&#41;. When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.\r\n\r\nWindows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows 2000 Service Pack 4 and Small Business Server 2000:\r\nFile Name\tVersion\tDate\tTime\tSize\r\n\r\nMsieftp.dll\r\n\t\r\n\r\n5.50.4956.500\r\n\t\r\n\r\n05-Aug-2005\r\n\t\r\n\r\n20:53\r\n\t\r\n\r\n248,592\r\n\r\nVerifying that the Update Has Been Applied\r\n\u2022\t\r\n\r\nMicrosoft Baseline Security Analyzer\r\n\r\nTo verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.\r\n\u2022\t\r\n\r\nFile Version Verification\r\n\r\nNote Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, and then click Search.\r\n\r\n2.\r\n\t\r\n\r\nIn the Search Results pane, click All files and folders under Search Companion.\r\n\r\n3.\r\n\t\r\n\r\nIn the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.\r\n\r\n4.\r\n\t\r\n\r\nIn the list of files, right-click a file name from the appropriate file information table, and then click Properties.\r\n\r\nNote Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.\r\n\r\n5.\r\n\t\r\n\r\nOn the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.\r\n\r\nNote Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.\r\n\u2022\t\r\n\r\nRegistry Key Verification\r\n\r\nYou may also be able to verify the files that this security update has installed by reviewing the following registry key:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Internet Explorer 6&#92;SP1&#92;KB905495-IE6SP1-20050805.184113&#92;Filelist\r\n\r\nNote This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the 905495 security update into the Windows installation source files.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\r\nObtaining Other Security Updates:\r\n\r\nUpdates for other security issues are available at the following locations:\r\n\u2022\t\r\n\r\nSecurity updates are available in the Microsoft Download Center. You can find them most easily by doing a keyword search for &quot;security_patch.&quot;\r\n\u2022\t\r\n\r\nUpdates for consumer platforms are available at the Windows Update Web site.\r\n\r\nSupport:\r\n\u2022\t\r\n\r\nCustomers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.\r\n\u2022\t\r\n\r\nInternational customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.\r\n\r\nSecurity Resources:\r\n\u2022\t\r\n\r\nThe Microsoft TechNet Security Web site provides additional information about security in Microsoft products.\r\n\u2022\t\r\n\r\nMicrosoft Software Update Services\r\n\u2022\t\r\n\r\nMicrosoft Windows Server Update Services\r\n\u2022\t\r\n\r\nMicrosoft Baseline Security Analyzer &#40;MBSA&#41;\r\n\u2022\t\r\n\r\nWindows Update\r\n\u2022\t\r\n\r\nMicrosoft Update\r\n\u2022\t\r\n\r\nWindows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.\r\n\u2022\t\r\n\r\nOffice Update \r\n\r\nSoftware Update Services:\r\n\r\nBy using Microsoft Software Update Services &#40;SUS&#41;, administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.\r\n\r\nFor more information about how to deploy security updates by using Software Update Services, visit the Software Update Services Web site.\r\n\r\nWindows Server Update Services:\r\n\r\nBy using Windows Server Update Services &#40;WSUS&#41;, administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems.\r\n\r\nFor more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server Update Services Web site.\r\n\r\nSystems Management Server:\r\n\r\nMicrosoft Systems Management Server &#40;SMS&#41; delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.\r\n\r\nNote SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scanning Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool &#40;available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack&#41; to install these updates.\r\n\r\nDisclaimer:\r\n\r\nThe information provided in the Microsoft Knowledge Base is provided &quot;as is&quot; without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.\r\n\r\nRevisions: \r\n\u2022\t\r\n\r\nV1.0 &#40;October 11, 2005&#41;: Bulletin published", "edition": 1, "reporter": "Securityvulns", "published": "2005-10-12T00:00:00", "title": "Microsoft Security Bulletin MS05-044 Vulnerability in the Windows FTP Client Could Allow File Transfer Location Tampering &#40;905495&#41;", "type": "securityvulns", "enchantments": {"score": {"modified": "2018-08-31T11:10:14", "vector": "NONE", "value": 5.0}}, "bulletinFamily": "software", "affectedSoftware": [], "cvelist": ["CVE-2005-2126"], "modified": "2005-10-12T00:00:00", "id": "SECURITYVULNS:DOC:9913", "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:9913", "cvss": {"score": 2.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:NONE/I:PARTIAL/A:NONE/"}}], "nessus": [{"lastseen": "2018-09-01T23:49:11", "references": ["https://technet.microsoft.com/library/security/ms05-044"], "pluginID": "19997", "description": "The remote host contains a version of the Microsoft FTP client that contains a flaw in the way it handles FTP download. An attacker could exploit this flaw to modify the destination location for files downloaded via FTP.\n\nTo exploit this flaw an attacker would need to set up a rogue FTP server and have a victim on the remote host connect to it and download a file manually using the affected client.", "edition": 6, "reporter": "Tenable", "published": "2005-10-11T00:00:00", "title": "MS05-044: Vulnerability in the Windows FTP Client Could Allow File Transfer Location Tampering (905495)", "type": "nessus", "enchantments": {"score": {"vector": "NONE", "value": 7.5}}, "naslFamily": "Windows : Microsoft Bulletins", "bulletinFamily": "scanner", "cvelist": ["CVE-2005-2126"], "modified": "2018-07-27T00:00:00", "cpe": ["cpe:/o:microsoft:windows"], "id": "SMB_NT_MS05-044.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=19997", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(19997);\n script_version(\"1.32\");\n script_cvs_date(\"Date: 2018/07/27 18:38:16\");\n\n script_cve_id(\"CVE-2005-2126\");\n script_bugtraq_id(12160);\n script_xref(name:\"MSFT\", value:\"MS05-044\");\n script_xref(name:\"CERT\", value:\"415828\");\n script_xref(name:\"MSKB\", value:\"905495\");\n\n script_name(english:\"MS05-044: Vulnerability in the Windows FTP Client Could Allow File Transfer Location Tampering (905495)\");\n script_summary(english:\"Determines the presence of update 905495\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"A flaw in the FTP client installed on the remote host could allow a\nrogue FTP server to write to arbitrary locations on the remote host.\");\n script_set_attribute(attribute:\"description\", value:\n\"The remote host contains a version of the Microsoft FTP client that\ncontains a flaw in the way it handles FTP download. An attacker could\nexploit this flaw to modify the destination location for files\ndownloaded via FTP.\n\nTo exploit this flaw an attacker would need to set up a rogue FTP server\nand have a victim on the remote host connect to it and download a file\nmanually using the affected client.\");\n script_set_attribute(attribute:\"see_also\", value:\"https://technet.microsoft.com/library/security/ms05-044\");\n script_set_attribute(attribute:\"solution\", value:\n\"Microsoft has released a set of patches for Windows 2000, XP and\n2003.\");\n script_set_cvss_base_vector(\"CVSS2#AV:N/AC:H/Au:N/C:N/I:P/A:N\");\n script_set_cvss_temporal_vector(\"CVSS2#E:U/RL:OF/RC:C\");\n script_set_attribute(attribute:\"exploitability_ease\", value:\"No known exploits are available\");\n script_set_attribute(attribute:\"exploit_available\", value:\"false\");\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2005/10/11\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2005/10/11\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2005/10/11\");\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:microsoft:windows\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n\n script_copyright(english:\"This script is Copyright (C) 2005-2018 Tenable Network Security, Inc.\");\n script_family(english:\"Windows : Microsoft Bulletins\");\n\n script_dependencies(\"smb_hotfixes.nasl\", \"ms_bulletin_checks_possible.nasl\");\n script_require_keys(\"SMB/MS_Bulletin_Checks/Possible\");\n script_require_ports(139, 445, 'Host/patch_management_checks');\n exit(0);\n}\n\ninclude(\"audit.inc\");\ninclude(\"smb_func.inc\");\ninclude(\"smb_hotfixes.inc\");\ninclude(\"smb_hotfixes_fcheck.inc\");\ninclude(\"misc_func.inc\");\n\nget_kb_item_or_exit(\"SMB/MS_Bulletin_Checks/Possible\");\n\nbulletin = 'MS05-044';\nkb = '905495';\n\nkbs = make_list(kb);\nif (get_kb_item(\"Host/patch_management_checks\")) hotfix_check_3rd_party(bulletin:bulletin, kbs:kbs, severity:SECURITY_NOTE);\n\nget_kb_item_or_exit(\"SMB/Registry/Enumerated\");\nget_kb_item_or_exit(\"SMB/WindowsVersion\", exit_code:1);\n\nif (hotfix_check_sp_range(win2k:'4,5', xp:'1', win2003:'0') <= 0) audit(AUDIT_OS_SP_NOT_VULN);\n\nversion = hotfix_check_ie_version();\nif (!version) exit(1, \"Failed to get the version of Internet Explorer.\");\nif (!egrep(pattern:\"^6\\.\", string:version)) exit(0, \"The installed version of Internet Explorer is not 6.x.\");\n\nrootfile = hotfix_get_systemroot();\nif (!rootfile) exit(1, \"Failed to get the system root.\");\n\nshare = hotfix_path2share(path:rootfile);\nif (!is_accessible_share(share:share)) audit(AUDIT_SHARE_FAIL, share);\n\nif (\n hotfix_is_vulnerable(os:\"5.2\", sp:0, file:\"msieftp.dll\", version:\"6.0.3790.383\", dir:\"\\system32\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.1\", sp:1, file:\"msieftp.dll\", version:\"6.0.2800.1724\", dir:\"\\system32\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.0\", file:\"msieftp.dll\", version:\"5.50.4956.500\", min_version:\"5.50.0.0\", dir:\"\\system32\", bulletin:bulletin, kb:kb)\n)\n{\n set_kb_item(name:\"SMB/Missing/\"+bulletin, value:TRUE);\n hotfix_security_note();\n hotfix_check_fversion_end();\n exit(0);\n}\nelse\n{\n hotfix_check_fversion_end();\n audit(AUDIT_HOST_NOT, 'affected');\n}\n", "cvss": {"score": 2.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:NONE/I:PARTIAL/A:NONE/"}}]}