GHSA-95v5-prp4-5gv5
Backstage vulnerable to potential reading of SCM URLs using built in token
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | @backstage/integration | < 1.20.1 | 1.20.1 |
Details
As written in the advisory (Markdown source, shown as plain text).
### Impact
A vulnerability in the SCM URL parsing used by Backstage integrations allowed path traversal sequences in encoded form to be included in file paths. When these URLs were processed by integration functions that construct API URLs, the traversal segments could redirect requests to unintended SCM provider API endpoints using the configured server-side integration credentials.
This affects instances that use any of the SCM integrations (GitHub, Bitbucket Server, Bitbucket Cloud) with the scaffolder or other features that accept user-provided SCM URLs.
### Patches
This is patched in `@backstage/integration` version 1.20.1.
### Workarounds
There is no workaround for this vulnerability. Users should upgrade to the patched version.
### References
- Backstage SCM integration documentation: https://backstage.io/docs/integrations/
References
External links from the advisory. They lead to third-party sites.