isolated-vm up to 3.x on Node.js API dynamically-managed code resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in isolated-vm up to 3.x on Node.js. Affected by this issue is some unknown functionality of the component API. The manipulation leads to dynamically-managed code resources. This vulnerability is traded as CVE-2021-21413. Access to the local network is required for this attack to succeed. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in isolated-vm up to 3.x on Node.js (JavaScript Library). This issue affects an unknown functionality of the component API. The manipulation with an unknown input leads to a dynamically-managed code resources vulnerability. Using CWE to declare the problem leads to CWE-913. The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements. Impacted is confidentiality, integrity, and availability.
The weakness was shared 03/31/2021. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2021-21413. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 4.0.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. 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
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
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: Dynamically-managed code resourcesCWE: CWE-913
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: isolated-vm 4.0.0
Patch: github.com
Timeline
12/22/2020 🔍03/31/2021 🔍
03/31/2021 🔍
04/07/2021 🔍
Sources
Advisory: github.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2021-21413 (🔍)
GCVE (CVE): GCVE-0-2021-21413
GCVE (VulDB): GCVE-100-172019
Entry
Created: 03/31/2021 07:28Updated: 04/07/2021 09:49
Changes: 03/31/2021 07:28 (41), 04/07/2021 09:45 (6), 04/07/2021 09:49 (1)
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.