Elasticsearch up to 5.6.14/6.6.0 Document Level Security permission

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.7$0-$5k0.00

Summaryinfo

A vulnerability was found in Elasticsearch up to 5.6.14/6.6.0. It has been rated as critical. This vulnerability affects unknown code of the component Document Level Security. This manipulation causes permission. This vulnerability appears as CVE-2019-7611. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability has been found in Elasticsearch up to 5.6.14/6.6.0 and classified as critical. Affected by this vulnerability is an unknown function of the component Document Level Security. The manipulation with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

A permission issue was found in Elasticsearch versions before 5.6.15 and 6.6.1 when Field Level Security and Document Level Security are disabled and the _aliases, _shrink, or _split endpoints are used . If the elasticsearch.yml file has xpack.security.dls_fls.enabled set to false, certain permission checks are skipped when users perform one of the actions mentioned above, to make existing data available under a new index/alias name. This could result in an attacker gaining additional permissions against a restricted index.

The bug was discovered 03/26/2019. The weakness was presented 03/25/2019. This vulnerability is known as CVE-2019-7611 since 02/07/2019. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1222 according to MITRE ATT&CK.

Upgrading to version 5.6.15 or 6.6.1 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.8
VulDB Meta Temp Score: 6.7

VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.1
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Permission
CWE: CWE-275 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Elasticsearch 5.6.15/6.6.1

Timelineinfo

02/07/2019 🔍
03/25/2019 +46 days 🔍
03/26/2019 +1 days 🔍
03/26/2019 +0 days 🔍
08/07/2023 +1595 days 🔍

Sourcesinfo

Advisory: discuss.elastic.co
Status: Not defined

CVE: CVE-2019-7611 (🔍)
GCVE (CVE): GCVE-0-2019-7611
GCVE (VulDB): GCVE-100-132223

Entryinfo

Created: 03/26/2019 14:11
Updated: 08/07/2023 12:21
Changes: 03/26/2019 14:11 (53), 05/20/2020 09:08 (1), 08/07/2023 12:21 (4)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

 Anonymous User
(+0)
7 years ago
Can you clarify versions affected? according to this there are more versions affected:

https://www.securityfocus.com/bid/107112

Elasticsearch Elasticsearch 6.6
Elasticsearch Elasticsearch 6.5.4
Elasticsearch Elasticsearch 6.5.3
Elasticsearch Elasticsearch 6.5.2
Elasticsearch Elasticsearch 6.5.1
Elasticsearch Elasticsearch 6.5
Elasticsearch Elasticsearch 5.6.14
Elasticsearch Elasticsearch 5.6.4
Elasticsearch Elasticsearch 1.7
Elasticsearch Elasticsearch 1.6.1
Elasticsearch Elasticsearch 1.6
Elasticsearch Elasticsearch 1.5.2
Elasticsearch Elasticsearch 1.5.1
Elasticsearch Elasticsearch 1.5
Elasticsearch Elasticsearch 1.4.5
Elasticsearch Elasticsearch 1.4.4
Elasticsearch Elasticsearch 1.4.3
Elasticsearch Elasticsearch 1.4.2
Elasticsearch Elasticsearch 1.4
Elasticsearch Elasticsearch 1.3.8
Elasticsearch Elasticsearch 1.3.7
Elasticsearch Elasticsearch 1.3
Elasticsearch Elasticsearch 1.1
Elasticsearch Elasticsearch 1.0
Elasticsearch Elasticsearch 2.3.3
Elasticsearch Elasticsearch 1.4.1
Elasticsearch Elasticsearch 1.2.0
Elasticsearch Elasticsearch 1.2
Elasticsearch Elasticsearch 1.1.1
the mod team is going to update the entry in the next 30 minutes

Want to stay up to date on a daily basis?

Enable the mail alert feature now!