CVE-2024-26150: `@backstage/backend-common` vulnerable to path traversal through symlinks

Published Feb 23, 2024
·
Updated

Impact

Paths checks with the resolveSafeChildPath utility were not exhaustive enough, leading to risk of path traversal vulnerabilities if symlinks can be injected by attackers.

Patches Patched in @backstage/backend-common version 0.21.1. Patched in @backstage/backend-common version 0.20.2. Patched in @backstage/backend-common version 0.19.10.

For more information If you have any questions or comments about this advisory:

- Open an issue in the Backstage repository - Visit our Discord, linked to in Backstage README

Other sources

@backstage/backend-common is a common functionality library for backends for Backstage, an open platform for building developer portals. In @backstage/backend-common prior to versions 0.21.1, 0.20.2, and 0.19.10, paths checks with the resolveSafeChildPath utility were not exhaustive enough, leading to risk of path traversal vulnerabilities if symlinks can be injected by attackers. This issue is patched in @backstage/backend-common versions 0.21.1, 0.20.2, and 0.19.10.

NVD

Affected Software

6 affected componentsFixes available
npm/@backstage/backend-common>=0.20.0<0.20.2
0.20.2
npm/@backstage/backend-common<0.19.10
0.19.10
npm/@backstage/backend-common=0.21.0
0.21.1
linuxfoundation Backstage Backend-common Node.js<0.19.10
linuxfoundation Backstage Backend-common Node.js>=0.20.0<0.20.2
linuxfoundation Backstage Backend-common Node.js=0.21.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@backstage/backend-common to a version that resolves this vulnerability.

    Fixed in 0.20.2
  2. Upgrade

    Upgrade npm/@backstage/backend-common to a version that resolves this vulnerability.

    Fixed in 0.19.10
  3. Upgrade

    Upgrade npm/@backstage/backend-common to a version that resolves this vulnerability.

    Fixed in 0.21.1
  4. Upgrade

    Upgrade @backstage/backend-common to a version that resolves this vulnerability.

    Fixed in 0.19.10
  5. Upgrade

    Upgrade @backstage/backend-common to a version that resolves this vulnerability.

    Fixed in 0.20.2
  6. Upgrade

    Upgrade @backstage/backend-common to a version that resolves this vulnerability.

    Fixed in 0.21.1

Event History

Feb 23, 2024
CVE Published
via MITRE·03:46 PM
Data Sourced
via MITRE·03:46 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
RemedyAffected Software
Advisory Published
via GitHub·06:02 PM
Data Sourced
via GitHub·06:02 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-26150?

CVE-2024-26150 is a vulnerability that poses risks for path traversal attacks due to inadequate path checks.

2

How do I fix CVE-2024-26150?

To fix CVE-2024-26150, upgrade to version 0.21.1 or higher of the @backstage/backend-common package.

3

What versions are affected by CVE-2024-26150?

CVE-2024-26150 affects versions 0.19.10 and up to 0.20.2 of the @backstage/backend-common package.

4

What are the potential impacts of CVE-2024-26150?

The potential impacts of CVE-2024-26150 include exploitation by attackers to perform unauthorized path traversal actions.

5

Is CVE-2024-26150 specific to any platform?

CVE-2024-26150 specifically affects the Backstage application running on Node.js.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203