CVE-2021-21413 Vulnerability Analysis & Exploit Details

CVE-2021-21413
Vulnerability Scoring

8.0
/10
Very High Risk

Highly exploitable, CVE-2021-21413 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Adjacent_network
    Attack Vector Under Analysis
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2021-21413 Details

Status: Modified

Last updated: 🕠 21 Nov 2024, 05:48 UTC
Originally published on: 🕚 30 Mar 2021, 23:15 UTC

Time between publication and last update: 1331 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

CVE-2021-21413 Vulnerability Summary

CVE-2021-21413: isolated-vm is a library for nodejs which gives you access to v8's Isolate interface. Versions of isolated-vm before v4.0.0 have API pitfalls which may make it easy for implementers to expose supposed secure isolates to the permissions of the main nodejs isolate. Reference objects allow access to the underlying reference's full prototype chain. In an environment where the implementer has exposed a Reference instance to an attacker they would be able to use it to acquire a Reference to the nodejs context's Function object. Similar application-specific attacks could be possible by modifying the local prototype of other API objects. Access to NativeModule objects could allow an attacker to load and run native code from anywhere on the filesystem. If combined with, for example, a file upload API this would allow for arbitrary code execution. This is addressed in v4.0.0 through a series of related changes.

Assessing the Risk of CVE-2021-21413

Access Complexity Graph

The exploitability of CVE-2021-21413 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2021-21413

CVE-2021-21413 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2021-21413, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2021-21413, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2021-21413 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2021-21413 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2021-21413 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.141% (probability of exploit)

EPSS Percentile: 51.27% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 48.73% of others.

CVE-2021-21413 References

External References

CWE Common Weakness Enumeration

CWE-913

Vulnerable Configurations

  • cpe:2.3:a:isolated-vm_project:isolated-vm:0.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:0.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:0.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:0.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:0.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:0.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:0.1.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:0.1.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:0.1.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:0.1.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:0.1.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:0.1.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.4.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.4.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.5.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.5.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.5.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.5.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.6.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.6.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:1.7.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:2.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:2.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:2.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:2.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:2.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:2.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:2.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:2.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:2.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:2.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:2.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:2.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.1.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.1.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.1.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.1.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:isolated-vm_project:isolated-vm:3.3.10:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2021-21413: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-31203 – An integer overflow was addressed with improved input validation. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, iPadOS 17.7.6, macOS Sonoma...
  • CVE-2025-31202 – A null pointer dereference was addressed with improved input validation. This issue is fixed in iOS 18.4 and iPadOS 18.4, macOS Sequoia 15.4, tvOS ...
  • CVE-2025-31197 – The issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, macOS Ventura 13.7.5, iPadOS 17.7.6, macOS Sono...
  • CVE-2025-30445 – A type confusion issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, macOS Ventura 13.7.5, iPadOS 17.7....
  • CVE-2025-24271 – An access issue was addressed with improved access restrictions. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, macOS Ventura 13.7.5, iPadOS...