CVE-2017-15103

A security-check flaw was found in the way the Heketi 5 server API handled user requests. An authenticated Heketi user could send specially crafted requests to the Heketi server, resulting in remote command execution as the user running Heketi server and possibly privilege escalation.

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

CVE-2017-15103 is rated High Risk (70.4/100): CVSS High severity, with high exploitation likelihood (EPSS 5.50%, 92th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +3.07% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize 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-15103

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 2.43% 5.50% +3.07%
2 2026-04-05 1.05% 2.43% +1.38%
3 2026-02-16 — 1.05% —

Full EPSS history (16 records total)

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

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]
9.0 2.0 HIGH
AV:N/AC:L/Au:S/C:C/I:C/A:C 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:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 8.0 10.0 [email protected]

Weakness enumeration for CVE-2017-15103

GitHub Security Advisory for CVE-2017-15103

OS Trackers for CVE-2017-15103

vendor priority summary link
redhat high — https://access.redhat.com/security/cve/CVE-2017-15103

Affected software / configurations for CVE-2017-15103

Vendor Product Version Raw CPE
heketi_project heketi 5.0 cpe:2.3:a:heketi_project:heketi:5.0:*:*:*:*:*:*:*
redhat enterprise_linux 7.0 cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*

References for CVE-2017-15103

cvelogic Threat Intelligence