Unrestricted File Upload in @backstage/techdocs-common (CVE-2021-32660)
Summary
Vulnerability in @backstage/techdocs-common (CVE-2021-32660). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.6.4 or later.
Original description
The description as published by the source.
Impact
A malicious internal actor is able to upload documentation content with malicious scripts. These scripts would normally be sanitized by the TechDocs frontend, but by tricking a user to visit the content via the TechDocs API, the content sanitazion will be bypassed. If the TechDocs API is hosted on the same origin as the Backstage app or other backend plugins, this may give access to sensitive data.
The ability to upload malicious content may be limited by internal code review processes, unless the chosen TechDocs deployment method is to use an object store and the actor has access to upload files directly to that store.
Patches
The vulnerability is patched in the 0.6.4 release of @backstage/techdocs-common.
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-32660 has been found in @backstage/techdocs-common.
Successful exploitation can lead to full system takeover.
What to do: upgrade @backstage/techdocs-common to 0.6.4 or later.
If unsure, ask your IT team or search "@backstage/techdocs-common CVE-2021-32660" on the vendor's site.
CVE-2021-32660 (@backstage/techdocs-common) — CWE-434
Attack vector: remote (network-reachable)
Patched: 0.6.4 — 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-434) exists in @backstage/techdocs-common.
Check the vendor advisory for the affected versions of @backstage/techdocs-common.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 0.6.4.
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/techdocs-common' . 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/techdocs-common' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@backstage/techdocs-commonを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @backstage/techdocs-common to 0.6.4ステージング環境で 0.6.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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