Skip to content

GHSA-2g8g-63j4-9w3r

RCE vulnerability affecting v1beta3 templates in @backstage/plugin-scaffolder-backend

High npm
Severity
High
The publisher's own rating, not a CVSS score
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
—
Not classified
Fix
0.15.14
Upgrade @backstage/plugin-scaffolder-backend to this version or later

Description

The templating library used by the scaffolder backend assumes that templates are trusted which is an undesired property of the scaffolder-backend. This has now been mitigated by sandboxing the template code execution.

Impact

A malicious actor with write access to a registered scaffolder template could manipulate the template in a way that allows for remote code execution on the scaffolder-backend instance. This was only exploitable in the template yaml definition itself and not by user input data.

Patches

This is vulnerability is patched in version 0.15.14 of @backstage/plugin-scaffolder-backend.

For more information

If you have any questions or comments about this advisory:

Affected versions

npm

PackageVulnerableFixed in
@backstage/plugin-scaffolder-backend
< 0.15.14
0.15.14

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

@backstage/plugin-scaffolder-backend npm → 0.15.14

npm
npm install @backstage/plugin-scaffolder-backend@0.15.14
yarn
yarn add @backstage/plugin-scaffolder-backend@0.15.14
pnpm
pnpm add @backstage/plugin-scaffolder-backend@0.15.14

References

Timeline

  1. Last updated by the source
  2. Published
AdvisorySeverityWhy it's related
GHSA-vwp5-f99x-x3rq
Backstage has improper input validation in scaffolder task list ordering
Medium Also affects @backstage/plugin-scaffolder-backend
GHSA-4xvq-3m68-h444
Backstage has sensitive information exposure in scaffolder task logs
Medium Also affects @backstage/plugin-scaffolder-backend
GHSA-hmp2-4m7g-22cv
Backstage: Scaffolder action input authorization bypass
High Also affects @backstage/plugin-scaffolder-backend
GHSA-95p4-vv4g-jxxm
Backstage may expose sensitive information in Scaffolder task failure events
Medium Also affects @backstage/plugin-scaffolder-backend
GHSA-g2v8-7jhw-pp8p
Backstage: Sensitive information exposure in Scaffolder
Critical Also affects @backstage/plugin-scaffolder-backend
GHSA-xvgh-hmx8-9xxf
Backstage: Improper task state validation in Scaffolder backend
High Also affects @backstage/plugin-scaffolder-backend
GHSA-mfvq-x7vr-rgqg
Backstage: Secret-derived values may be exposed in scaffolder task logs
Medium Also affects @backstage/plugin-scaffolder-backend
GHSA-29gx-h2m3-xw44
Backstage's scaffolder credential handling may allow unintended GitHub authentication fallback
Medium Also affects @backstage/plugin-scaffolder-backend
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor