Backstage catalog rules can be bypassed for URL locations using encoded path segments
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Reports 1
1 outlet mention it. Reports are not confirmation; each links to its source.
Description
Backstage is an open framework for building developer portals. Prior to 3.9.2 and from 4.0.0 until 4.0.2, DefaultCatalogRulesEnforcer in @backstage/plugin-catalog-backend compares the raw location.target URL against catalog.rules, while URL readers canonicalize the same URL before fetching it. An authenticated user with catalog.location.create permission can use percent-encoded path segments to make an untrusted URL match a trusted location pattern even though the canonical URL resolves outside that scope. This admits entity content from an untrusted source as trusted, while further downstream consequences depend on deployment configuration. This issue is fixed in versions 3.9.2 and 4.0.2.
Text from CVE List
Affected versions 2
- backstageaffected: < 3.9.2CVE List
- backstageaffected: >= 4.0.0, < 4.0.2CVE List
References 5
- github.com/backstage/backstage/commit/3214dc8f15d4a08a2fd07a72a8fe4d00aeac0db4Fixvia CVE List
- github.com/backstage/backstage/commit/737ff1c719dbd5a97f375b7f1db6d61416618419Fixvia CVE List
- github.com/backstage/backstage/releases/tag/v1.54.10Fixvia CVE List
- github.com/backstage/backstage/releases/tag/v1.56.1Fixvia CVE List
- github.com/backstage/backstage/security/advisories/GHSA-w658-mh9p-ww8fAdvisoryvia CVE List