Skip to content

GHSA-c77j-p484-h84m BIT-elasticsearch-2020-7019 CVE-2020-7019

Improper privilege management in elasticsearch

Medium Maven
Severity
6.5 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
1.40%
Chance of exploitation in the next 30 days. Higher than 72.57% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-269 Improper Privilege Management
Fix
7.9.0
Upgrade org.elasticsearch:elasticsearch to this version or later

Description

In Elasticsearch before 7.9.0 and 6.8.12 a field disclosure flaw was found when running a scrolling search with Field Level Security. If a user runs the same query another more privileged user recently ran, the scrolling search can leak fields that should be hidden. This could result in an attacker gaining additional permissions against a restricted index.

Affected versions

Maven

PackageVulnerableFixed in
org.elasticsearch:elasticsearch
>= 7.0.0, < 7.9.0
7.9.0
org.elasticsearch:elasticsearch
< 6.8.12
6.8.12

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.9.0

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

Severity breakdown

CVSS 3.1 6.5

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

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

Weakness

CWE-269: Improper Privilege Management

The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that 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: Follow the principle of least privilege when assigning access rights to entities in a software system.
  • Architecture and Design: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.

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