Elastic Code 7.3.0/7.3.1/7.3.2 Repository Import permission assignment
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Elastic Code 7.3.0/7.3.1/7.3.2. It has been rated as problematic. Impacted is an unknown function of the component Repository Import Handler. This manipulation causes permission assignment. This vulnerability is tracked as CVE-2019-7618. The attack is possible to be carried out remotely. No exploit exists. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability has been found in Elastic Code 7.3.0/7.3.1/7.3.2 and classified as problematic. Affected by this vulnerability is an unknown function of the component Repository Import Handler. The manipulation with an unknown input leads to a permission assignment vulnerability. The CWE definition for the vulnerability is CWE-732. The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. As an impact it is known to affect confidentiality. The summary by CVE is:
A local file disclosure flaw was found in Elastic Code versions 7.3.0, 7.3.1, and 7.3.2. If a malicious code repository is imported into Code it is possible to read arbitrary files from the local filesystem of the Kibana instance running Code with the permission of the Kibana system user.
The weakness was disclosed 10/01/2019. This vulnerability is known as CVE-2019-7618 since 02/07/2019. The attack can be launched remotely. The successful exploitation requires a single authentication. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: Permission assignmentCWE: CWE-732 / 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/07/2019 🔍10/01/2019 🔍
10/02/2019 🔍
12/29/2023 🔍
Sources
Advisory: discuss.elastic.coStatus: Not defined
CVE: CVE-2019-7618 (🔍)
GCVE (CVE): GCVE-0-2019-7618
GCVE (VulDB): GCVE-100-142807
Entry
Created: 10/02/2019 08:31 AMUpdated: 12/29/2023 02:14 PM
Changes: 10/02/2019 08:31 AM (35), 09/18/2020 12:09 PM (17), 12/29/2023 02:14 PM (3)
Complete: 🔍
Cache ID: 244:766:40
No comments yet. Languages: en.
Please log in to comment.