[+] Credits: John Page AKA hyp3rlinx [+] Website: hyp3rlinx.altervista.org [+] Source: http://hyp3rlinx.altervista.org/advisories/FTP-VOYAGER-SCHEDULER-CSRF-REMOTE-CMD-EXECUTION.txt [+] ISR: ApparitionSec Vendor: ============== solarwinds.com www.serv-u.com Product: ==================== FTP Voyager Scheduler v16.2.0 Vulnerability Type: ============================= CSRF Remote Command Execution CVE Reference: ============== CVE-2017-6803 Security Issue: ================ Multiple cross site request forgeries exist in the Web Interface side of FTP Voyager Scheduler running on port 52986. Allowing remote attackers to make HTTP requests on behalf of an authenticated user if that user visits a malicious webpage or clicks an attacker supplied link. FTP Voyager has a scheduler feature that lets users create tasks/commands to execute on some type of other action like when Directorys are created, files uploaded/downloader, Scheduler starts or stops and so forth. Remote attackers who successfully pull off CSRF exploitation can do things like change the Admin password or cause a persistent Denial of Service by setting the task to terminate "FTP Voyager Scheduler" itself upon startup among other nefarious things. Exploit/POC: ============= Default login no password, then set a password in FTP Voyager Scheduler Web interface. Upon CSRF the user will get a HTTP Response will be like below, we can prevent user from seeing this message targeting hidden iframe in webpage. 0Operation was successful.141175 1) Change Admin passwd
2) Persistent Denial Of Service uses call to WMIC
Network Access: =============== Remote Severity: ========= High Disclosure Timeline: ======================================= Vendor Notification: November 30, 2016 Result: No Reply Second Notification Attempt: March 5, 2017 Result: March 9, 2017 : Public Disclosure [+] Disclaimer The information contained within this advisory is supplied "as-is" with no warranties or guarantees of fitness of use or otherwise. Permission is hereby granted for the redistribution of this advisory, provided that it is not altered except by reformatting it, and that due credit is given. Permission is explicitly given for insertion in vulnerability databases and similar, provided that due credit is given to the author. The author is not responsible for any misuse of the information contained herein and accepts no responsibility for any damage caused by the use or misuse of this information. The author prohibits any malicious use of security related information or exploits by the author or elsewhere. All content (c) hyp3rlinx