← Back
CVE-2020-29565
Vulnerability in horizon (CVE-2020-29565)
Summary
vulnerability in horizon (CVE-2020-29565). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `15.3.2, 16.2.1, 18.3.3, 18.6.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2020-29565** has been found in horizon.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade horizon to **15.3.2, 16.2.1, 18.3.3, 18.6.0** or later.
If unsure, ask your IT team or search "horizon CVE-2020-29565" on the vendor's site.
CVE-2020-29565 (horizon) —
Patched: `15.3.2, 16.2.1, 18.3.3, 18.6.0` — 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.
❓ What is the problem
**A vulnerability** (unclassified) exists in horizon.
📍 Affected scope
horizon — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **15.3.2, 16.2.1, 18.3.3, 18.6.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'horizon' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'horizon' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `horizon` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade horizon to 15.3.2, 16.2.1, 18.3.3, 18.6.0ステージング環境で 15.3.2, 16.2.1, 18.3.3, 18.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
horizon
[{"type":"ECOSYSTEM","events":[{"introduced":"15.3.0"},{"fixed":"15.3.2"},{"introduced":"16.0.0"},{"fixed":"16.2.1"},{"introduced":"17.0.0"},{"fixed":"18.3.3"},{"introduced":"18.4.0"},{"fixed":"18.6.0"}]}]
References
- advisory https://www.debian.org/security/2020/dsa-4820
- advisory https://github.com/advisories/GHSA-f8fh-xp28-q59m
- web https://bugs.launchpad.net/horizon/+bug/1865026
- web https://review.opendev.org/c/openstack/horizon/+/758841/
- web https://review.opendev.org/c/openstack/horizon/+/758843/
- web https://security.openstack.org/ossa/OSSA-2020-008.html
- web http://www.openwall.com/lists/oss-security/2020/12/08/2