Interpretation conflict in WinSCP before 4.0.4 allows remote attackers to perform arbitrary file transfers with a remote server via file-transfer commands in the final portion of a (1) scp, and possibly a (2) sftp or (3) ftp, URL, as demonstrated by a URL specifying login to the remote server with a username of scp, which is interpreted as an HTTP scheme name by the protocol handler in a web browser, but is interpreted as a username by WinSCP. NOTE: this is related to an incomplete fix for CVE-2006-3015.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Winscp | Winscp | 2.0.0 (including) | 2.0.0 (including) |
Winscp | Winscp | 3.5.5_beta (including) | 3.5.5_beta (including) |
Winscp | Winscp | 3.5.6 (including) | 3.5.6 (including) |
Winscp | Winscp | 3.6 (including) | 3.6 (including) |
Winscp | Winscp | 3.6.1 (including) | 3.6.1 (including) |
Winscp | Winscp | 3.6.5_beta (including) | 3.6.5_beta (including) |
Winscp | Winscp | 3.6.6 (including) | 3.6.6 (including) |
Winscp | Winscp | 3.6.7 (including) | 3.6.7 (including) |
Winscp | Winscp | 3.8.1 (including) | 3.8.1 (including) |
Winscp | Winscp | 3.8.2 (including) | 3.8.2 (including) |
Winscp | Winscp | 4.0.2 (including) | 4.0.2 (including) |
Winscp | Winscp | 4.0.3 (including) | 4.0.3 (including) |