JetBrains VIM Plugin up to 0.51 Project File vim_settings.xml sensitive information
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in JetBrains VIM Plugin up to 0.51. It has been classified as problematic. This affects an unknown function of the file vim_settings.xml of the component Project File Handler. This manipulation causes sensitive information. This vulnerability is tracked as CVE-2019-14957. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic was found in JetBrains VIM Plugin up to 0.51 (Word Processing Software). Affected by this vulnerability is an unknown code block of the file vim_settings.xml of the component Project File Handler. The manipulation with an unknown input leads to a sensitive information vulnerability. The CWE definition for the vulnerability is CWE-922. The product stores sensitive information without properly limiting read or write access by unauthorized actors. As an impact it is known to affect confidentiality. The summary by CVE is:
The JetBrains Vim plugin before version 0.52 was storing individual project data in the global vim_settings.xml file. This xml file could be synchronized to a publicly accessible GitHub repository.
The weakness was disclosed 10/01/2019 (Website). The advisory is shared at blog.jetbrains.com. This vulnerability is known as CVE-2019-14957 since 08/12/2019. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
By approaching the search of inurl:vim_settings.xml it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 0.52 eliminates this vulnerability.
The entries VDB-142773, VDB-142775, VDB-142781 and VDB-142831 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 0.1
- 0.2
- 0.3
- 0.4
- 0.5
- 0.6
- 0.7
- 0.8
- 0.9
- 0.10
- 0.11
- 0.12
- 0.13
- 0.14
- 0.15
- 0.16
- 0.17
- 0.18
- 0.19
- 0.20
- 0.21
- 0.22
- 0.23
- 0.24
- 0.25
- 0.26
- 0.27
- 0.28
- 0.29
- 0.30
- 0.31
- 0.32
- 0.33
- 0.34
- 0.35
- 0.36
- 0.37
- 0.38
- 0.39
- 0.40
- 0.41
- 0.42
- 0.43
- 0.44
- 0.45
- 0.46
- 0.47
- 0.48
- 0.49
- 0.50
- 0.51
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
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: Sensitive informationCWE: CWE-922 / CWE-200 / CWE-284
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: VIM Plugin 0.52
Timeline
08/12/2019 🔍10/01/2019 🔍
10/01/2019 🔍
09/18/2020 🔍
Sources
Advisory: blog.jetbrains.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2019-14957 (🔍)
GCVE (CVE): GCVE-0-2019-14957
GCVE (VulDB): GCVE-100-142777
See also: 🔍
Entry
Created: 10/01/2019 21:35Updated: 09/18/2020 08:48
Changes: 10/01/2019 21:35 (59), 09/18/2020 08:48 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.