{"vuid":"VU#912588","idnumber":"912588","name":"WinSCP URI handlers fails to properly parse command line switches","keywords":["WinSCP","URI handlers","parse","command line switches"],"overview":"A vulnerability has been found in WinSCP, which can be exploited by an attacker to overwrite or add files to the victim's computer.","clean_desc":"WinSCP is an open source SFTP client for Microsoft windows. It supports a file-manager user interface, and uses the SSH protocol to transfer files between hosts. If an attacker convinces a user to follow a specially crafted URL, a file may be directly transferred to the user's computer. The attacker may also be able to append information to files. Depending on what the user interface settings of WinSCP are, user-interaction may or may not be required to complete the file transfer. This vulnerability is a result of certain command line switches being passed to WinSCP in the malicious URL.","impact":"If a victim user clicks on the specially-crafted URL, an attacker could send any chosen file to the victim's computer with access to folders that the user running WinSCP has write access to. The attacker could also append information to a file that may damage the file or make it unusable.","resolution":"Upgrade Version 3.8.2 of WinSCP has been published and contains a fix for this vulnerability. Users are encouraged to upgrade to this version of the software.","workarounds":"Restrict Access Limit SSH client access to trusted servers. SSH servers usually listens on 22/tcp, but can be configured to listen on any TCP port. Require User Interaction for File Transfers WinSCP can be configured to notify the user of all file transfers and not automatically handle scp:// and sftp:// addresses. Users are encouraged to enable these options.","sysaffected":"","thanks":"This vulnerability was reported b\ny \nJelmer Kuperus","author":"This document was written by Ryan Giobbi.","public":["http://secunia.com/advisories/20575/","http://lists.grok.org.uk/pipermail/full-disclosure/2006-June/046810.html"],"cveids":["CVE-2006-3015"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2006-06-12T12:53:32Z","publicdate":"2006-06-11T00:00:00Z","datefirstpublished":"2006-06-22T15:01:25Z","dateupdated":"2006-07-07T18:11:52Z","revision":16,"vrda_d1_directreport":"0","vrda_d1_population":"2","vrda_d1_impact":"2","cam_widelyknown":"17","cam_exploitation":"1","cam_internetinfrastructure":"4","cam_population":"6","cam_impact":"8","cam_easeofexploitation":"2","cam_attackeraccessrequired":"20","cam_scorecurrent":"0.792","cam_scorecurrentwidelyknown":"0.9","cam_scorecurrentwidelyknownexploited":"1.584","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":0.792,"vulnote":null}