Skip to content
Fencer Intel
medium 5.0

CVE-2015-5531 json

Improper Limitation of a Pathname to a Restricted Directory in Elasticsearch

published 11y ago modified 4mo ago also GHSA-jjq8-vfjq-j6v4 , EUVD-2022-4392

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
94.8%
EPSS 94.8% chance of exploitation in 30 days, percentile 99.8%
public exploits
2
Metasploit and Exploit-DB, plus a Nuclei check

Summary

Directory traversal vulnerability in Elasticsearch before 1.6.1 allows remote attackers to read arbitrary files via unspecified vectors related to snapshot API calls.

Patch / fix

  • maven org.elasticsearch:elasticsearch 1.6.1

Is CVE-2015-5531 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-5531 updated cvss 1.9

elasticsearch: directory traversal attack

  • Red Hat Satellite 6 elasticsearch Red Hat Subscription Asset Manager elasticsearch
    not affected: vulnerable code not present “Constrain access to the snapshot API to trusted sources.”

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-38383)

Exploit prediction

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

Exploits and checks

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.elasticsearch:elasticsearch
<1.6.1
1.6.1

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.