CVE-2015-3337: Improper Limitation of a Pathname to a Restricted Directory in Elasticsearch
Summary
CVE-2015-3337: Improper Limitation of a Pathname to a Restricted Directory in Elasticsearch. Affects org.elasticsearch:elasticsearch across 2 version ranges.
< 1.4.5
>= 1.5.0, < 1.5.2
Fixed in 1.4.5 or 1.5.2, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Elasticsearch is a distributed, RESTful search and analytics engine built on Apache Lucene. It provides a scalable solution for indexing and searching large amounts of data. This vulnerability affects versions before 1.4.5 and 1.5.x before 1.5.2 of the Elasticsearch package. When a site plugin is enabled, remote attackers can exploit a directory traversal vulnerability to read arbitrary files on the system.
Vulnerability Detail
The vulnerability in Elasticsearch allows attackers to traverse directories and read arbitrary files on the system. This can lead to unauthorized access to sensitive information, such as configuration files or user data. The exact vectors of attack are unspecified. The vulnerability has a moderate severity rating and is classified under CWE-22.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
< 1.4.51.4.5 -
>= 1.5.0, < 1.5.21.5.2
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. However, as a general security practice, it is recommended to follow the principle of least privilege and restrict access to sensitive files and directories. Regularly monitoring and reviewing access logs can help detect any unauthorized access attempts.
Conclusion
The vulnerability in Elasticsearch allows remote attackers to read arbitrary files on the system. Upgrading to the recommended versions and securing access permissions can mitigate the risk. For further support on vulnerability remediation, contact DevNack.com.
See every vulnerability recorded for org.elasticsearch:elasticsearch →
FAQ
Elasticsearch is a distributed, RESTful search and analytics engine built on Apache Lucene. It provides a scalable solution for indexing and searching large amounts of data.
The vulnerability allows remote attackers to read arbitrary files on the system, potentially leading to unauthorized access to sensitive information.
To fix this vulnerability, upgrade to Elasticsearch version 1.4.5 or 1.5.2, depending on the affected version. Additionally, review and secure access permissions of sensitive files and directories.
There is no specific workaround mentioned for this vulnerability. However, following security best practices such as restricting access to sensitive files and monitoring access logs can help mitigate the risk.
The vulnerability has a moderate severity rating.
Related vulnerabilities
Recent vulnerabilities recorded for org.elasticsearch:elasticsearch.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.