Vulnerability in isolated-vm (CVE-2021-21413)
Summary
Vulnerability in isolated-vm (CVE-2021-21413). Confidential information can be exposed externally. Exploitable via Reference. Mitigation: upgrade to 4.0.0 or later.
Original description
The description as published by the source.
Versions of isolated-vm before v4.0.0, and especially before v3.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.
To address these issues the following changes were made in v4.0.0:
- Documentation was updated with more explicit guidelines on building secure applications.
Referenceinstances will no longer follow prototype chains by default, nor will they invoke accessors or proxies.- All
isolated-vmAPI prototypes are now immutable. NativeModuleconstructor may only be invoked from a nodejs isolate.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-21413 has been found in isolated-vm.
Attackers can target a specific entry point like Reference over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade isolated-vm to 4.0.0 or later.
If unsure, ask your IT team or search "isolated-vm CVE-2021-21413" on the vendor's site.
CVE-2021-21413 (isolated-vm) — CWE-913
Attack vector: adjacent-network / unauthenticated / no user interaction
Attack surface: Reference / Function / NativeModule
Patched: 4.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-913) exists in isolated-vm. Attackers reach the vulnerable code path via Reference without authentication.
Check the vendor advisory for the affected versions of isolated-vm. Attack surface: Reference / Function / NativeModule.
Severity: ?. Confidential information can be exposed externally.
Update to 4.0.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'isolated-vm' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'isolated-vm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
isolated-vmを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade isolated-vm to 4.0.0ステージング環境で 4.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com