Cross-Site Scripting (XSS) in Octopus Deploy (CVE-2017-16810)
Summary
Cross-site scripting in Octopus Deploy (CVE-2017-16810). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.13.7 or later.
Original description
The description as published by the source.
Cross-site scripting (XSS) vulnerability in the All Variables tab in Octopus Deploy 3.4.0-3.13.6 (fixed in 3.13.7) allows remote attackers to inject arbitrary web script or HTML via the Variable Set Name parameter.
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-16810 has been found in Octopus Deploy.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade Octopus Deploy to 3.13.7 or later.
If unsure, ask your IT team or search "Octopus Deploy CVE-2017-16810" on the vendor's site.
CVE-2017-16810 (Octopus Deploy) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Patched: 3.13.7 — apply immediately
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.
Cross-site scripting (XSS) (CWE-79) exists in Octopus Deploy.
Check the vendor advisory for the affected versions of Octopus Deploy.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 3.13.7.
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・依存マニフェストで Octopus Deploy を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Octopus Deploy to 3.13.7ステージング環境で 3.13.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit github.com