Path Traversal in @backstage/techdocs-common (CVE-2021-32662)
Summary
Path traversal in @backstage/techdocs-common (CVE-2021-32662). Confidential information can be exposed externally. Exploitable via docs_dir. Mitigation: upgrade to 0.6.3 or later.
Original description
The description as published by the source.
Impact
A malicious actor could read sensitive files from the environment where TechDocs documentation is built and published by setting a particular path for docs_dir in mkdocs.yml. These files would then be available over the TechDocs backend API.
This vulnerability is mitigated by the fact that an attacker would need access to modify the mkdocs.yml in the documentation source code, and would also need access to the TechDocs backend API.
Patches
The vulnerability is patched in the 0.6.3 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-32662 has been found in @backstage/techdocs-common.
Attackers can target a specific entry point like docs_dir over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade @backstage/techdocs-common to 0.6.3 or later.
If unsure, ask your IT team or search "@backstage/techdocs-common CVE-2021-32662" on the vendor's site.
CVE-2021-32662 (@backstage/techdocs-common) — CWE-22
Attack vector: remote (network-reachable) / no user interaction
Attack surface: docs_dir
Patched: 0.6.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.
Path traversal (CWE-22) exists in @backstage/techdocs-common. Attackers reach the vulnerable code path via docs_dir.
Check the vendor advisory for the affected versions of @backstage/techdocs-common. Attack surface: docs_dir.
Severity: ?. Confidential information can be exposed externally.
Update to 0.6.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 '@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.3ステージング環境で 0.6.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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