Cross-Site Request Forgery (CSRF) in SolarWinds (formerly Serv-U) FTP Voyager (CVE-2017-6803)
Summary
Vulnerability in SolarWinds (formerly Serv-U) FTP Voyager (CVE-2017-6803). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
Multiple cross-site request forgery (CSRF) vulnerabilities in the web interface in the Scheduler in SolarWinds (formerly Serv-U) FTP Voyager 16.2.0 allow remote attackers to hijack the authentication of users for requests that (1) change the admin password, (2) terminate the scheduler, or (3) possibly execute arbitrary commands via crafted requests to Admin/XML/Result.xml.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2017-6803 has been found in SolarWinds (formerly Serv-U) FTP Voyager.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "SolarWinds (formerly Serv-U) FTP Voyager CVE-2017-6803" on the vendor's site.
CVE-2017-6803 (SolarWinds (formerly Serv-U) FTP Voyager) — CWE-352 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in SolarWinds (formerly Serv-U) FTP Voyager.
Check the vendor advisory for the affected versions of SolarWinds (formerly Serv-U) FTP Voyager.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで SolarWinds (formerly Serv-U) FTP Voyager を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory securityfocus.com
- exploit hyp3rlinx.altervista.org
- exploit packetstormsecurity.com
- exploit exploit-db.com