Insecure sandbox in Backstage Scaffolder plugin
cve-program · CVE-2023-35926
PublishedBackstage is an open platform for building developer portals. The Backstage scaffolder-backend plugin uses a templating library that requires sandbox, as it by design allows for code injection. The library used for this sandbox so far has been `vm2`, but in light of several past vulnerabilities and existing vulnerabilities that may not have a fix, the plugin has switched to using a different sandbox library. 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. This is vulnerability is fixed in version 1.15.0 of `@backstage/plugin-scaffolder-backend`.
Read the publisher's advisoryeuvd · EUVD-2023-1899
PublishedBackstage is an open platform for building developer portals. The Backstage scaffolder-backend plugin uses a templating library that requires sandbox, as it by design allows for code injection. The library used for this sandbox so far has been `vm2`, but in light of several past vulnerabilities and existing vulnerabilities that may not have a fix, the plugin has switched to using a different sandbox library. 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. This is vulnerability is fixed in version 1.15.0 of `@backstage/plugin-scaffolder-backend`.
Read the publisher's advisorynvd · CVE-2023-35926
PublishedBackstage is an open platform for building developer portals. The Backstage scaffolder-backend plugin uses a templating library that requires sandbox, as it by design allows for code injection. The library used for this sandbox so far has been `vm2`, but in light of several past vulnerabilities and existing vulnerabilities that may not have a fix, the plugin has switched to using a different sandbox library. 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. This is vulnerability is fixed in version 1.15.0 of `@backstage/plugin-scaffolder-backend`.
Read the publisher's advisoryosv · GHSA-wg6p-jmpc-xjmr
PublishedThe Backstage scaffolder-backend plugin uses a templating library that requires a sandbox, as it by design allows for code injection. The library used for this sandbox so far has been `vm2`, but in light of several past vulnerabilities and existing vulnerabilities that may not have a fix, the plugin has switched to using a different sandbox library. ### 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 fixed in version 1.15.0 of `@backstage/plugin-scaffolder-backend`. ### Workarounds Note that the [Backstage Threat Model](https://backstage.io/docs/overview/threat-model) states that scaffolder templates are considered to be a sensitive area that with the recommendation that you control access and perform manual reviews of changes to the scaffolder templates. The exploit is of a nature where it is easily discoverable in manual review.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2023-35926 · CVE overview and exploitation status
cve-program · CVE-2023-35926
- https://github.com/backstage/backstage/security/advisories/GHSA-wg6p-jmpc-xjmr
- https://github.com/backstage/backstage/commit/fb7375507d56faedcb7bb3665480070593c8949a
- https://github.com/backstage/backstage/releases/tag/v1.15.0
euvd · EUVD-2023-1899
- https://github.com/backstage/backstage/security/advisories/GHSA-wg6p-jmpc-xjmr
- https://github.com/backstage/backstage/commit/fb7375507d56faedcb7bb3665480070593c8949a
- https://github.com/backstage/backstage/releases/tag/v1.15.0
nvd · CVE-2023-35926
- https://github.com/backstage/backstage/commit/fb7375507d56faedcb7bb3665480070593c8949a
- https://github.com/backstage/backstage/releases/tag/v1.15.0
- https://github.com/backstage/backstage/security/advisories/GHSA-wg6p-jmpc-xjmr
osv · GHSA-wg6p-jmpc-xjmr
- https://github.com/backstage/backstage/security/advisories/GHSA-wg6p-jmpc-xjmr
- https://nvd.nist.gov/vuln/detail/CVE-2023-35926
- https://github.com/backstage/backstage/commit/fb7375507d56faedcb7bb3665480070593c8949a
- https://github.com/backstage/backstage
- https://github.com/backstage/backstage/releases/tag/v1.15.0
Related changes
Linked by CVE identifierNo related changes are available here.