GHSA-w94p-6mhw-4qxw CVE-2015-1427
Improper Access Control in Elasticsearch
- Severity
- High
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- 99.91%
- Chance of exploitation in the next 30 days. Higher than 99.97% of scored vulnerabilities.
- Known exploited
- Yes
- In CISA's catalog since Mar 25, 2022
- Weakness
- CWE-284 Improper Access Control
- Fix
1.3.8- Upgrade org.elasticsearch:elasticsearch to this version or later
Description
The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands via a crafted script.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.elasticsearch:elasticsearch | < 1.3.8 |
1.3.8 |
| org.elasticsearch:elasticsearch | >= 1.4.0, < 1.4.3 |
1.4.3 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
org.elasticsearch:elasticsearch Maven → 1.3.8
- maven
<dependency><groupId>org.elasticsearch</groupId><artifactId>elasticsearch</artifactId><version>1.3.8</version></dependency>- gradle
implementation("org.elasticsearch:elasticsearch:1.3.8")
Weakness
CWE-284: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How to prevent it
- Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Other links
- access.redhat.com/errata/RHSA-2017:0868
- exchange.xforce.ibmcloud.com/vulnerabilities/100850
- elastic.co/community/security
- packetstormsecurity.com/files/130368/Elasticsearch-1.3.7-1.4.2-Sandbox-Escape-Command-Execut…
- packetstormsecurity.com/files/130784/ElasticSearch-Unauthenticated-Remote-Code-Execution.html
- elasticsearch.com/blog/elasticsearch-1-4-3-1-3-8-released
Timeline
- Added to CISA's Known Exploited Vulnerabilities catalog
- Remediation due for U.S. federal agencies
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-mrfm-jxgf-2h6v Elasticsearch Improper Access Control vulnerability | High Known exploited | Also affects org.elasticsearch:elasticsearch |
| GHSA-mm3m-5497-xggg Elasticsearch Uncontrolled Resource Consumption Vulnerability | High | Also affects org.elasticsearch:elasticsearch |
| GHSA-5xm9-x7x4-4j5x Elasticsearch Vulnerable to Stack Overflow due to a Large Recursion | High | Also affects org.elasticsearch:elasticsearch |
| GHSA-jgx4-7v3v-vwfm Elasticsearch allocation of resources without limits or throttling leads to crash | High | Also affects org.elasticsearch:elasticsearch |
| GHSA-5mpw-4546-2wcr Elasticsearch Incorrect Authorization vulnerability | Medium | Also affects org.elasticsearch:elasticsearch |
| GHSA-5v8f-xx9m-wj44 Elasticsearch stores private key on disk unencrypted | High | Also affects org.elasticsearch:elasticsearch |
| GHSA-2hjr-vmf3-xwvp Elasticsearch Insertion of Sensitive Information into Log File | Medium | Also affects org.elasticsearch:elasticsearch |
| GHSA-4q22-422g-m4pj Elasticsearch StackOverflow vulnerability | Medium | Also affects org.elasticsearch:elasticsearch |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor