Backstage Linux Foundation Backstage

Do you want an email whenever new security vulnerabilities are reported in Linux Foundation Backstage?

By the Year

In 2024 there have been 1 vulnerability in Linux Foundation Backstage with an average score of 5.7 out of ten. Last year Backstage had 1 security vulnerability published. If vulnerabilities keep coming in at the current rate, it appears that number of security vulnerabilities in Backstage in 2024 could surpass last years number. Last year, the average CVE base score was greater by 4.20

Year Vulnerabilities Average Score
2024 1 5.70
2023 1 9.90
2022 0 0.00
2021 2 5.70
2020 0 0.00
2019 0 0.00
2018 0 0.00

It may take a day or so for new Backstage vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Linux Foundation Backstage Security Vulnerabilities

A flaw was found in the Red Hat Developer Hub (RHDH)

CVE-2023-6944 5.7 - Medium - January 04, 2024

A flaw was found in the Red Hat Developer Hub (RHDH). The catalog-import function leaks GitLab access tokens on the frontend when the base64 encoded GitLab token includes a newline at the end of the string. The sanitized error can display on the frontend, including the raw access token. Upon gaining access to this token and depending on permissions, an attacker could push malicious code to repositories, delete resources in Git, revoke or generate new keys, and sign code illegitimately.

Generation of Error Message Containing Sensitive Information

Backstage is an open platform for building developer portals

CVE-2023-35926 9.9 - Critical - June 22, 2023

Backstage 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`.

Code Injection

Backstage is an open platform for building developer portals

CVE-2021-41151 4.9 - Medium - October 18, 2021

Backstage is an open platform for building developer portals. In affected versions A malicious actor could read sensitive files from the environment where Scaffolder Tasks are run. The attack is executed by crafting a custom Scaffolder template with a `github:publish:pull-request` action and a particular source path. When the template is executed the sensitive files would be included in the published pull request. This vulnerability is mitigated by the fact that an attacker would need access to create and register templates in the Backstage catalog, and that the attack is very visible given that the exfiltration happens via a pull request. The vulnerability is patched in the `0.15.9` release of `@backstage/plugin-scaffolder-backend`.

Directory traversal

Backstage is an open platform for building developer portals, and techdocs-common contains common functionalities for Backstage's TechDocs

CVE-2021-32662 6.5 - Medium - June 03, 2021

Backstage is an open platform for building developer portals, and techdocs-common contains common functionalities for Backstage's TechDocs. In `@backstage/techdocs-common` versions prior to 0.6.3, a malicious actor could read sensitive files from the environment where TechDocs documentation is built and published by setting a particular path for `docs_dir` in `mkdocs.yml`. These files would then be available over the TechDocs backend API. This vulnerability is mitigated by the fact that an attacker would need access to modify the `mkdocs.yml` in the documentation source code, and would also need access to the TechDocs backend API. The vulnerability is patched in the `0.6.3` release of `@backstage/techdocs-common`.

Directory traversal

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Linux Foundation Backstage or by Linux Foundation? Click the Watch button to subscribe.

subscribe