Horde Image API vulnerabilitiesRanked by how likely they are to be used.
Horde Image API is made by Horde. We track 2 published vulnerabilities in it, across 23 versions. None of them is on the list of flaws known to be exploited today. If you run Horde Image API, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Horde Image API vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Horde Image API's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Horde Image API flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 4.0%CVE-2017-14650High
A Remote Code Execution vulnerability has been found in the Horde_Image library when using the "Im" backend that utilizes ImageMagick's "convert" utility.
- 2.4%CVE-2017-9774High
Remote Code Execution was found in Horde_Image 2.x before 2.5.0 via a crafted GET request.
Running Horde Image API? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Horde Image API on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 2 published vulnerabilities listed under the name Horde Image API, across 23 versions.
None of Horde Image API's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Horde Image API. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.