vscode-bazel up to 0.4.0 JSON Config File file inclusion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in vscode-bazel up to 0.4.0. This affects an unknown part of the component JSON Config File Handler. The manipulation leads to file inclusion. This vulnerability is listed as CVE-2021-22539. The attack must be carried out locally. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in vscode-bazel up to 0.4.0. This issue affects an unknown functionality of the component JSON Config File Handler. The manipulation with an unknown input leads to a file inclusion vulnerability. Using CWE to declare the problem leads to CWE-73. The product allows user input to control or influence paths or file names that are used in filesystem operations. Impacted is confidentiality, integrity, and availability.
The weakness was presented 04/16/2021. The advisory is shared at github.com. The identification of this vulnerability is CVE-2021-22539. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.4.1 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: File inclusionCWE: CWE-73
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: vscode-bazel 0.4.1
Patch: github.com
Timeline
01/05/2021 🔍04/16/2021 🔍
04/16/2021 🔍
04/21/2021 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2021-22539 (🔍)
GCVE (CVE): GCVE-0-2021-22539
GCVE (VulDB): GCVE-100-173153
Entry
Created: 04/16/2021 14:35Updated: 04/21/2021 18:24
Changes: 04/16/2021 14:35 (37), 04/21/2021 18:20 (5), 04/21/2021 18:24 (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.