CVE-2015-4165Not scoredCWE-264

CVE-2015-4165: Elasticsearch vulnerability

Elasticsearch

Affected: Elasticsearch · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

4.5%probability of exploitation in the next 30 days

91st percentile

050100

Higher than 91% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

The snapshot API in Elasticsearch before 1.6.0 when another application exists on the system that can read Lucene files and execute code from them, is accessible by the attacker, and the Java VM on which Elasticsearch is running can write to a location that the other application can read and execute from, allows remote authenticated users to write to and create arbitrary snapshot metadata files, and potentially execute arbitrary code.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Permissions, Privileges, and Access Controls · Access Control
Vendor: Elasticsearch
Published: August 2017
Band: Possible (1 to 10%), August 2017

CoverageNo articles yet

No CyberSIXT article names CVE-2015-4165 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.