CVE-2018-17247

Elasticsearch Security versions 6.5.0 and 6.5.1 contain an XXE flaw in Machine Learning's find_file_structure API. If a policy allowing external network access has been added to Elasticsearch's Java Security Manager then an attacker could send a specially crafted request capable of leaking content of local files on the Elasticsearch node. This could allow a user to access information that they should not have access to.

Published: 2018-12-20 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2018-17247 is rated Moderate Risk (48.7/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.38%). Core evidence: EPSS rose +1.08% over the last day, indicating growing attacker interest. Mandatory action: 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-2018-17247

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 0.31% 1.38% +1.08%
2 2025-10-28 0.35% 0.31% -0.05%
3 2025-10-27 0.35%

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-17247

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.9 3.0 MEDIUM
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N 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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
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:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
2.2 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
8.6 2.9 [email protected]

Weakness enumeration for CVE-2018-17247

GitHub Security Advisory for CVE-2018-17247

GHSA-ccmr-qj26-845g · Severity: medium · Ecosystem: maven — Improper Restriction of XML External Entity Reference in Elasticsearch

OS Trackers for CVE-2018-17247

vendor priority summary link
ubuntu low CVE-2018-17247 low priority: Ubuntu including 1 source packages (elasticsearch), 6 status rows across 6 suites (bionic, cosmic, disco, trusty, upstream, xenial): DNE 4, not-affected 2. https://ubuntu.com/security/CVE-2018-17247

Affected software / configurations for CVE-2018-17247

Vendor Product Version Raw CPE
elastic elasticsearch 6.5.0 cpe:2.3:a:elastic:elasticsearch:6.5.0:*:*:*:*:*:*:*
elastic elasticsearch 6.5.1 cpe:2.3:a:elastic:elasticsearch:6.5.1:*:*:*:*:*:*:*

References for CVE-2018-17247

cvelogic Threat Intelligence