GHSA-rg9r-hr7g-5gc2: Path Traversal
Impact
An authenticated user with access to one TechDocs documentation site could craft a URL able to read documentation belonging to a different entity. This only affects deployments using the external TechDocs builder with an external storage provider (S3, GCS, etc.) and the permission framework enabled. Instances that do not use the permission framework are unaffected, since TechDocs content is visible to all authenticated users by design.
Patches
Patched in @backstage/plugin-techdocs-backend version 2.2.4
Workarounds
- None other than upgrading. Deployments that serve TechDocs from local storage are not affected.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@backstage/plugin-techdocs-backendto a version that resolves this vulnerability.Fixed in 2.2.4 - Upgrade
Upgrade
@backstage/plugin-techdocs-backendto a version that resolves this vulnerability.Fixed in 2.2.4
Event History
Frequently Asked Questions
Which deployments are affected?
Affected deployments use the external TechDocs builder, an external storage provider such as S3 or GCS, and have the permission framework enabled. Deployments serving TechDocs from local storage are not affected, and deployments without the permission framework are unaffected because TechDocs content is intentionally visible to all authenticated users.
What access does an attacker need?
An attacker must be an authenticated user who can access at least one TechDocs documentation site. They can then craft a URL to read documentation associated with a different entity.
What version fixes the issue?
Upgrade @backstage/plugin-techdocs-backend to version 2.2.4 or later. No workaround is provided other than upgrading.