Elastic Cloud Enterprise up to 1.1.3 Roles Token access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Elastic Cloud Enterprise up to 1.1.3 and classified as critical. This issue affects some unknown processing of the component Roles Token Handler. Executing a manipulation can lead to access control. This vulnerability is tracked as CVE-2018-3829. The attack can be launched remotely. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability classified as critical was found in Elastic Cloud Enterprise up to 1.1.3 (Cloud Software). This vulnerability affects an unknown code of the component Roles Token Handler. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
In Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 it was discovered that a user could scale out allocators on new hosts with an invalid roles token. An attacker with access to the previous runner ID and IP address of the coordinator-host could add a allocator to an existing ECE install to gain access to other clusters data.
The bug was discovered 06/13/2018. The weakness was disclosed 09/19/2018 (Website). The advisory is available at discuss.elastic.co. This vulnerability was named CVE-2018-3829 since 01/01/2018. The attack can be initiated remotely. A single authentication is needed for exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 98 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 1.1.4 eliminates this vulnerability.
The entries VDB-124278 and VDB-124281 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.1VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Cloud Enterprise 1.1.4
Timeline
01/01/2018 🔍06/13/2018 🔍
09/19/2018 🔍
09/19/2018 🔍
09/20/2018 🔍
03/25/2020 🔍
Sources
Advisory: discuss.elastic.coStatus: Not defined
Confirmation: 🔍
CVE: CVE-2018-3829 (🔍)
GCVE (CVE): GCVE-0-2018-3829
GCVE (VulDB): GCVE-100-124282
See also: 🔍
Entry
Created: 09/20/2018 08:27Updated: 03/25/2020 15:24
Changes: 09/20/2018 08:27 (60), 03/25/2020 15:24 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.