Skip to content
Fencer Intel
medium 4.3

CVE-2015-3337 json

Improper Limitation of a Pathname to a Restricted Directory in Elasticsearch

published 2015-05-01 11 y ago modified 2026-06-17 4 mo ago also GHSA-x8q8-4hp5-463w , EUVD-2022-5748

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
33.2%
EPSS 33.2% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

Directory traversal vulnerability in Elasticsearch before 1.4.5 and 1.5.x before 1.5.2, when a site plugin is enabled, allows remote attackers to read arbitrary files via unspecified vectors.

Patch / fix

  • maven org.elasticsearch:elasticsearch 1.4.5, 1.5.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-3337 updated cvss 1.9

elasticsearch: directory traversal flaw

  • Red Hat OpenShift Enterprise 2 openshift-origin-cartridge-fuse Red Hat Satellite 6 elasticsearch Red Hat Subscription Asset Manager elasticsearch
    under investigation

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Published
  2. First public exploit (EDB-37054)

Exploit prediction

33.16% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-37054 ElasticSearch < 1.4.5 / < 1.5.2 - Directory Traversal webapps, 2015-05-18
  • Nuclei template Elasticsearch - Local File Inclusion nuclei detection template
  • securityfocus.com http://www.securityfocus.com/bid/74353 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.elasticsearch:elasticsearch
<1.4.5
>=1.5.0, <1.5.2
1.4.5
1.5.2

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.