GHSA-g734-fhp4-7mfp: Infoleak
Impact
An authenticated internal user who can execute the affected actions may cause the backend to contact unintended destinations and disclose Sentry integration credentials. Subsequent impact depends on network reachability and the privileges granted to the configured token.
Patches
Upgrade @backstage/plugin-scaffolder-backend-module-sentry to version 0.3.8 or later. The fixed package is available in Backstage v1.54.8 and Backstage v1.55.0.
The update removes custom action-level apiBaseUrl values. Move any such value to scaffolder.sentry.apiBaseUrl before upgrading.
Workarounds
- Disable the affected actions until the patched package is deployed. - Restrict scaffolder.action.execute permission for the affected Sentry actions to trusted users and templates.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@backstage/plugin-scaffolder-backend-module-sentryto a version that resolves this vulnerability.Fixed in 0.3.8 - Upgrade
Upgrade
@backstage/plugin-scaffolder-backend-module-sentryto a version that resolves this vulnerability.Fixed in 0.3.8 - Configuration
Restrict scaffolder.action.execute permission for the affected Sentry actions to trusted users and templates.
Backstage Sentry scaffolder scaffolder.action.execute permission = trusted users and templates only - Configuration
Move any custom action-level apiBaseUrl value to scaffolder.sentry.apiBaseUrl before upgrading.
Backstage Sentry scaffolder scaffolder.sentry.apiBaseUrl = the custom API base URL - Compensating control
Disable the affected Sentry actions until the patched package is deployed.
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated internal user who can execute the affected Sentry actions can exploit it. Access to the scaffolder.action.execute permission for those actions is the relevant control point.
What could an attacker gain or do?
They may cause the backend to contact unintended destinations and disclose Sentry integration credentials. The resulting impact depends on what network locations the backend can reach and the privileges of the configured token.
What configuration change is required when upgrading?
Upgrade @backstage/plugin-scaffolder-backend-module-sentry to 0.3.8 or later. Before upgrading, move any custom action-level apiBaseUrl setting to scaffolder.sentry.apiBaseUrl, because the update removes custom action-level apiBaseUrl values.
What can be done before a patch is deployed?
Disable the affected actions, or restrict scaffolder.action.execute permission for the affected Sentry actions to trusted users and templates.