Skip to content

GHSA-hr65-qq6p-87r4 BIT-elasticsearch-2021-22137 CVE-2021-22137

Exposure of Sensitive Information to an Unauthorized Actor in Elasticsearch

Medium Maven
Severity
5.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
1.19%
Chance of exploitation in the next 30 days. Higher than 67.89% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-281 Improper Preservation of Permissions
Fix
7.11.2
Upgrade org.elasticsearch:elasticsearch to this version or later

Description

In Elasticsearch versions before 7.11.2 and 6.8.15 a document disclosure flaw was found when Document or Field Level Security is used. Search queries do not properly preserve security permissions when executing certain cross-cluster search queries. This could result in the search disclosing the existence of documents the attacker should not be able to view. This could result in an attacker gaining additional insight into potentially sensitive indices.

Affected versions

Maven

PackageVulnerableFixed in
org.elasticsearch:elasticsearch
>= 7.11.0, < 7.11.2
7.11.2
org.elasticsearch:elasticsearch
< 6.8.15
6.8.15

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 → 7.11.2

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

Severity breakdown

CVSS 3.1 5.3

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • 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.

CWE-281: Improper Preservation of Permissions

The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-mrfm-jxgf-2h6v
Elasticsearch Improper Access Control vulnerability
High Known exploited Also affects org.elasticsearch:elasticsearch
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
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