VSCodeVim up to 1.18.x Workspace Configuration privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in VSCodeVim up to 1.18.x. This vulnerability affects unknown code of the component Workspace Configuration Handler. Performing a manipulation results in an unknown weakness. This vulnerability is known as CVE-2021-28832. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in VSCodeVim up to 1.18.x. This affects some unknown processing of the component Workspace Configuration Handler. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 04/05/2021. It is possible to read the advisory at vuln.ryotak.me. This vulnerability is uniquely identified as CVE-2021-28832. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 1.19.0 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
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: Privilege escalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: VSCodeVim 1.19.0
Patch: github.com
Timeline
03/19/2021 🔍04/05/2021 🔍
04/05/2021 🔍
04/10/2021 🔍
Sources
Advisory: vuln.ryotak.meStatus: Confirmed
CVE: CVE-2021-28832 (🔍)
GCVE (CVE): GCVE-0-2021-28832
GCVE (VulDB): GCVE-100-172395
Entry
Created: 04/05/2021 12:53Updated: 04/10/2021 07:38
Changes: 04/05/2021 12:53 (36), 04/10/2021 07:36 (5), 04/10/2021 07:38 (18)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.