Skip to content

Path Traversal in @backstage/plugin-scaffolder-backend

Moderate severity GitHub Reviewed Published Oct 16, 2021 in backstage/backstage • Updated Feb 1, 2023

Package

npm @backstage/plugin-scaffolder-backend (npm)

Affected versions

>= 0.9.4, < 0.15.9

Patched versions

0.15.9

Description

Impact

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 publish:github:pull-request action using 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.

Patches

The vulnerability is patched in the 0.15.9 release of @backstage/plugin-scaffolder-backend.

For more information

If you have any questions or comments about this advisory:

References

@Rugvip Rugvip published to backstage/backstage Oct 16, 2021
Reviewed Oct 18, 2021
Published by the National Vulnerability Database Oct 18, 2021
Published to the GitHub Advisory Database Oct 19, 2021
Last updated Feb 1, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

EPSS score

0.071%
(32nd percentile)

Weaknesses

CVE ID

CVE-2021-41151

GHSA ID

GHSA-pvv8-8fx9-h673

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.