Vulnerability in zrender (CVE-2021-39227)
Summary
Vulnerability in zrender (CVE-2021-39227). Risk of unauthorized operations or information disclosure. Exploitable via merge. Mitigation: upgrade to 4.3.3 or later.
Original description
The description as published by the source.
Impact
Using merge and clone helper methods in the src/core/util.ts module will have prototype pollution. It will affect the popular data visualization library Apache ECharts, which is using and exported these two methods directly.
Patches
It has been patched in https://github.com/ecomfe/zrender/pull/826.
Users should update zrender to 5.2.1. and update echarts to 5.2.1 if project is using echarts.
References
NA
For more information
NA
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-39227 has been found in zrender.
Attackers can target a specific entry point like merge over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade zrender to 4.3.3 or later.
If unsure, ask your IT team or search "zrender CVE-2021-39227" on the vendor's site.
CVE-2021-39227 (zrender) — CWE-1321
Attack vector: local / unauthenticated / no user interaction
Attack surface: merge / clone
Patched: 4.3.3 — 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-1321) exists in zrender. Attackers reach the vulnerable code path via merge without authentication.
Check the vendor advisory for the affected versions of zrender. Attack surface: merge / clone.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.3.3.
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 'zrender' . 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 'zrender' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
zrenderを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade zrender to 4.3.3ステージング環境で 4.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com