# CVE-2017-14650: Command injection in n/a

> Remote code execution via command injection in Horde_Image library when using ImageMagick backend, affecting custom applications.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-14650, GHSA-fxvw-26c8-9g9m, UBUNTU-CVE-2017-14650

## What is CVE-2017-14650?

CVE-2017-14650 is a high-severity command injection vulnerability in n/a, published on 21 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-14650?

It affects 1 product.


Products: Horde Horde Image Api.

## How do I fix CVE-2017-14650?

Upgrade to a fixed version.

## Is CVE-2017-14650 being exploited?

There is no known exploitation of CVE-2017-14650 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-9774](https://insights.sbomify.com/CVE-2017-9774/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14650 and fix it if it is affected.

What it is: CVE-2017-14650 is a high-severity command injection vulnerability in n/a, published on 21 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14650 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-14650/ (Markdown: https://insights.sbomify.com/CVE-2017-14650/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-14650
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-14650
- OSV: https://osv.dev/vulnerability/CVE-2017-14650

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-14650/
Summaries are generated and may contain mistakes; the official description above is the record.