CVE-2017-9774

Remote Code Execution was found in Horde_Image 2.x before 2.5.0 via a crafted GET request. Exploitation requires authentication.

Published: 2017-06-21 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-9774 is rated Moderate Risk (61.9/100): CVSS High severity, with medium exploitation likelihood (EPSS 2.38%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-9774

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 4.25% 2.38% -1.86%
2 2026-05-10 5.33% 4.25% -1.08%
3 2026-02-22 — 5.33% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-9774

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
6.5 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.0 6.4 [email protected]

Weakness enumeration for CVE-2017-9774

OS Trackers for CVE-2017-9774

vendor priority summary link
debian not yet assigned CVE-2017-9774 not yet assigned priority: Debian including 1 source packages (php-horde-image), 3 status rows across 3 suites (bookworm, bullseye, sid): resolved 3. https://security-tracker.debian.org/tracker/CVE-2017-9774
ubuntu medium CVE-2017-9774 medium priority: Ubuntu including 1 source packages (php-horde-image), 20 status rows across 20 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial, yakkety, zesty): DNE 11, not-affected 4, ignored 3, needed 1, released 1. https://ubuntu.com/security/CVE-2017-9774

Affected software / configurations for CVE-2017-9774

Vendor Product Version Raw CPE
horde horde_image_api 2.0.0 cpe:2.3:a:horde:horde_image_api:2.0.0:*:*:*:*:*:*:*
horde horde_image_api 2.0.0 cpe:2.3:a:horde:horde_image_api:2.0.0:alpha1:*:*:*:*:*:*
horde horde_image_api 2.0.0 cpe:2.3:a:horde:horde_image_api:2.0.0:beta1:*:*:*:*:*:*
horde horde_image_api 2.0.0 cpe:2.3:a:horde:horde_image_api:2.0.0:beta2:*:*:*:*:*:*
horde horde_image_api 2.0.1 cpe:2.3:a:horde:horde_image_api:2.0.1:*:*:*:*:*:*:*
horde horde_image_api 2.0.2 cpe:2.3:a:horde:horde_image_api:2.0.2:*:*:*:*:*:*:*
horde horde_image_api 2.0.3 cpe:2.3:a:horde:horde_image_api:2.0.3:*:*:*:*:*:*:*
horde horde_image_api 2.0.4 cpe:2.3:a:horde:horde_image_api:2.0.4:*:*:*:*:*:*:*
horde horde_image_api 2.0.5 cpe:2.3:a:horde:horde_image_api:2.0.5:*:*:*:*:*:*:*
horde horde_image_api 2.0.6 cpe:2.3:a:horde:horde_image_api:2.0.6:*:*:*:*:*:*:*
horde horde_image_api 2.0.7 cpe:2.3:a:horde:horde_image_api:2.0.7:*:*:*:*:*:*:*
horde horde_image_api 2.0.8 cpe:2.3:a:horde:horde_image_api:2.0.8:*:*:*:*:*:*:*
horde horde_image_api 2.0.9 cpe:2.3:a:horde:horde_image_api:2.0.9:*:*:*:*:*:*:*
horde horde_image_api 2.1.0 cpe:2.3:a:horde:horde_image_api:2.1.0:*:*:*:*:*:*:*
horde horde_image_api 2.2.0 cpe:2.3:a:horde:horde_image_api:2.2.0:*:*:*:*:*:*:*
horde horde_image_api 2.3.0 cpe:2.3:a:horde:horde_image_api:2.3.0:*:*:*:*:*:*:*
horde horde_image_api 2.3.1 cpe:2.3:a:horde:horde_image_api:2.3.1:*:*:*:*:*:*:*
horde horde_image_api 2.3.2 cpe:2.3:a:horde:horde_image_api:2.3.2:*:*:*:*:*:*:*
horde horde_image_api 2.3.3 cpe:2.3:a:horde:horde_image_api:2.3.3:*:*:*:*:*:*:*
horde horde_image_api 2.3.4 cpe:2.3:a:horde:horde_image_api:2.3.4:*:*:*:*:*:*:*
horde horde_image_api 2.3.5 cpe:2.3:a:horde:horde_image_api:2.3.5:*:*:*:*:*:*:*
horde horde_image_api 2.3.6 cpe:2.3:a:horde:horde_image_api:2.3.6:*:*:*:*:*:*:*
horde horde_image_api 2.4.0 cpe:2.3:a:horde:horde_image_api:2.4.0:*:*:*:*:*:*:*
horde horde_image_api 2.4.1 cpe:2.3:a:horde:horde_image_api:2.4.1:*:*:*:*:*:*:*

References for CVE-2017-9774

cvelogic Threat Intelligence