Path Traversal in @node-red/runtime (CVE-2021-21298)
Summary
Path traversal in @node-red/runtime (CVE-2021-21298). Risk of unauthorized operations or information disclosure. Exploitable via projects.read. Mitigation: upgrade to 1.2.8 or later.
Original description
The description as published by the source.
Impact
This vulnerability allows arbitrary path traversal via the Projects API.
If the Projects feature is enabled, a user with projects.read permission is able to access any file via the Projects API.
Patches
The issue has been patched in Node-RED 1.2.8
Workarounds
The vulnerability applies only to the Projects feature which is not enabled by default in Node-RED.
The primary workaround is not give untrusted users read access to the Node-RED editor.
For more information
If you have any questions or comments about this advisory:
- Email us at team@nodered.org
Acknowledgements
Thanks to the Tencent Woodpecker Security Team for disclosing this vulnerability.
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-21298 has been found in @node-red/runtime.
Attackers can target a specific entry point like projects.read over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
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-21298" on the vendor's site.
CVE-2021-21298 (@node-red/runtime) — CWE-22
Attack surface: projects.read
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.
Path traversal (CWE-22) exists in @node-red/runtime. Attackers reach the vulnerable code path via projects.read.
Check the vendor advisory for the affected versions of @node-red/runtime. Attack surface: projects.read.
Severity: ?. Risk of unauthorized operations or information disclosure.
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 nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web npmjs.com