Skip to content

GHSA-mrfm-jxgf-2h6v CVE-2014-3120

Elasticsearch Improper Access Control vulnerability

High Known exploited Maven
Severity
8.1 / 10
High · CVSS 3.1
Exploit chance (EPSS)
88.56%
Chance of exploitation in the next 30 days. Higher than 99.77% of scored vulnerabilities.
Known exploited
Yes
In CISA's catalog since Mar 25, 2022
Weakness
CWE-284 Improper Access Control
Fix
1.4.0.Beta1
Upgrade org.elasticsearch:elasticsearch to this version or later
Exploited in the wild. Elasticsearch Remote Code Execution Vulnerability (Elastic Elasticsearch). Required action: Apply updates per vendor instructions. Due for U.S. federal agencies by Apr 15, 2022.

Description

The default configuration in Elasticsearch before 1.4.0.Beta1 enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code via the source parameter to _search. NOTE: this only violates the vendor's intended security policy if the user does not run Elasticsearch in its own independent virtual machine.

Affected versions

Maven

PackageVulnerableFixed in
org.elasticsearch:elasticsearch
< 1.4.0.Beta1
1.4.0.Beta1
org.elasticsearch:elasticsearch
< 1.4.0.Beta1
1.4.0.Beta1

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.4.0.Beta1

maven
<dependency><groupId>org.elasticsearch</groupId><artifactId>elasticsearch</artifactId><version>1.4.0.Beta1</version></dependency>
gradle
implementation("org.elasticsearch:elasticsearch:1.4.0.Beta1")

Severity breakdown

CVSS 3.1 8.1

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N/E:H

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None
Exploit maturity
H

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

Timeline

  1. Added to CISA's Known Exploited Vulnerabilities catalog
  2. Remediation due for U.S. federal agencies
  3. Published
  4. Last updated by the source
  5. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-w94p-6mhw-4qxw
Improper Access Control in Elasticsearch
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
Is this in your code?

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