Vulnerability in Horde (CVE-2017-14650)
Summary
Vulnerability in Horde (CVE-2017-14650). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.5.2 or later.
Original description
The description as published by the source.
A Remote Code Execution vulnerability has been found in the Horde_Image library when using the "Im" backend that utilizes ImageMagick's "convert" utility. It's not exploitable through any Horde application, because the code path to the vulnerability is not used by any Horde code. Custom applications using the Horde_Image library might be affected. This vulnerability affects all versions of Horde_Image from 2.0.0 to 2.5.1, and is fixed in 2.5.2. The problem is missing input validation of the index field in _raw() during construction of an ImageMagick command line.
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-14650 has been found in Horde.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: upgrade Horde to 2.5.2 or later.
If unsure, ask your IT team or search "Horde CVE-2017-14650" on the vendor's site.
CVE-2017-14650 (Horde) — CWE-20 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.5.2 — 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.
A vulnerability (CWE-20) exists in Horde.
Check the vendor advisory for the affected versions of Horde.
Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover.
Update to 2.5.2.
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. Run grep -r 'Horde' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Horde' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Hordeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Horde to 2.5.2ステージング環境で 2.5.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2017-14650 php-horde-image Fixed in: 2.5.2-1
References
- advisory openwall.com
- advisory marc.info
- exploit github.com
- web debian.org