Vulnerability in @node-red/runtime (CVE-2021-21297)
Summary
Vulnerability in @node-red/runtime (CVE-2021-21297). Data can be tampered with by attackers. Mitigation: upgrade to 1.2.8 or later.
Original description
The description as published by the source.
Node-Red is a low-code programming for event-driven applications built using nodejs. Node-RED 1.2.7 and earlier contains a Prototype Pollution vulnerability in the admin API. A badly formed request can modify the prototype of the default JavaScript Object with the potential to affect the default behaviour of the Node-RED runtime. The vulnerability is patched in the 1.2.8 release. A workaround is to ensure only authorized users are able to access the editor url.
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-21297 has been found in @node-red/runtime.
Data can be tampered with by attackers.
What to do: upgrade @node-red/runtime to 1.2.8 or later.
If unsure, ask your IT team or search "@node-red/runtime CVE-2021-21297" on the vendor's site.
CVE-2021-21297 (@node-red/runtime) — CWE-1321
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.2.8 — 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 @node-red/runtime.
Check the vendor advisory for the affected versions of @node-red/runtime.
Severity: ?. Data can be tampered with by attackers.
Update to 1.2.8.
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 '@node-red/runtime' . 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 '@node-red/runtime' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@node-red/runtimeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @node-red/runtime to 1.2.8ステージング環境で 1.2.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web npmjs.com
- web npmjs.com
- web npmjs.com
- web npmjs.com