backstage backend-common up to 0.19.9/0.20.1/0.21.0 resolveSafeChildPath path traversal

Summaryinfo

A vulnerability has been found in backstage backend-common up to 0.19.9/0.20.1/0.21.0 and classified as critical. Affected is the function resolveSafeChildPath. Performing a manipulation results in path traversal. This vulnerability is cataloged as CVE-2024-26150. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as critical, was found in backstage backend-common up to 0.19.9/0.20.1/0.21.0. This affects the function resolveSafeChildPath. The manipulation with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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

The weakness was shared 02/23/2024 as GHSA-2fc9-xpp8-2g9h. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-26150 since 02/14/2024. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

Upgrading to version 0.19.10, 0.20.2 or 0.21.1 eliminates this vulnerability. Applying the patch 1ad2b1b61ebb430051f7d804b0cc7ebfe7922b6f is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• backstage

Name

• backend-common

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9
• 0.10
• 0.11
• 0.12
• 0.13
• 0.14
• 0.15
• 0.16
• 0.17
• 0.18
• 0.19
• 0.19.0
• 0.19.1
• 0.19.2
• 0.19.3
• 0.19.4
• 0.19.5
• 0.19.6
• 0.19.7
• 0.19.8
• 0.19.9
• 0.20
• 0.20.0
• 0.20.1
• 0.21.0

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion