Path Traversal in @backstage/plugin-scaffolder-backend (CVE-2021-41151)
Summary
Path traversal in @backstage/plugin-scaffolder-backend (CVE-2021-41151). Confidential information can be exposed externally. Mitigation: upgrade to 0.15.9 or later.
Original description
The description as published by the source.
Impact
A malicious actor could read sensitive files from the environment where Scaffolder tasks are run. The attack is executed by crafting a custom Scaffolder template with a publish:github:pull-request action using a particular source path. When the template is executed the sensitive files would be included in the published pull request.
This vulnerability is mitigated by the fact that an attacker would need access to create and register templates in the Backstage catalog, and that the attack is very visible given that the exfiltration happens via a pull request.
Patches
The vulnerability is patched in the 0.15.9 release of @backstage/plugin-scaffolder-backend.
For more information
If you have any questions or comments about this advisory:
- Open an issue in the Backstage repository
- Visit our chat, linked to in Backstage README
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-41151 has been found in @backstage/plugin-scaffolder-backend.
Confidential information can be exposed externally.
What to do: upgrade @backstage/plugin-scaffolder-backend to 0.15.9 or later.
If unsure, ask your IT team or search "@backstage/plugin-scaffolder-backend CVE-2021-41151" on the vendor's site.
CVE-2021-41151 (@backstage/plugin-scaffolder-backend) — CWE-22
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.15.9 — 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 @backstage/plugin-scaffolder-backend.
Check the vendor advisory for the affected versions of @backstage/plugin-scaffolder-backend.
Severity: ?. Confidential information can be exposed externally.
Update to 0.15.9.
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 '@backstage/plugin-scaffolder-backend' . 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 '@backstage/plugin-scaffolder-backend' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@backstage/plugin-scaffolder-backendを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @backstage/plugin-scaffolder-backend to 0.15.9ステージング環境で 0.15.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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